Systems and methods for traffic inspection via an embedded browser

ABSTRACT

Described embodiments provide systems and methods for traffic inspection via embedded browsers. An application inspector module of an embedded browser executable on a client may intercept network traffic for an application. The network traffic may include packets exchanged between the application and the server via a channel. The application inspector module may identify a computing resource usage on the client in providing a user with access to the application via the embedded browser. The application inspector module may generate analytics data based on the intercepted network traffic and the computing resource usage. The application inspector module may maintain a user behavior profile based on the analytics data. The application inspector module may determine that a portion of the network traffic directed to the remote server contains sensitive information. Responsive to the determination, the application inspector module may block or remove the portion of the network traffic.

CROSS REFERENCES TO RELATED APPLICATIONS

This application is continuation of and claims priority to U.S. patentapplication Ser. No. 16/402,935, titled “SYSTEMS AND METHODS FOR TRAFFICINSPECTION VIA AN EMBEDDED BROWSER,” filed May 3, 2019, which claimspriority under 35 U.S.C. § 119(e) to U.S. Provisional Patent ApplicationNo. 62/667,211, titled “SYSTEMS AND METHODS FOR TRAFFIC INSPECTION VIAAN EMBEDDED BROWSER,” filed May 4, 2018, each of which are incorporatedherein by reference in entirety.

FIELD OF THE DISCLOSURE

The present application generally relates to traffic inspection,including but not limited to systems and methods for traffic inspectionvia embedded browsers.

BACKGROUND

A client may access resources of an application hosted on a cloudcomputing service at a prearranged quality of service. As the clientaccesses the resources of the application, performance and behavior datamay be gathered by the cloud computing service. An operator of theclient, however, may have difficulty determining whether the cloudcomputing service is providing the resources at the prearranged qualityof service.

BRIEF SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features, nor is it intended to limit the scope of the claimsincluded herewith.

When moving from a locally hosted setup to a remote server (e.g., aspart of Software as a Service (SaaS), Infrastructure as a Service(IaaS), and Platform as a Service (PaaS)), users may lose a degree ofcontrol over quality of service, management, and data flow to the remoteserver. As part of the move, there may be a prearranged set of operationconditions regarding performance (e.g., service level agreement). As aclient accesses resources of an application hosted on the remote server,the remote server may gather performance data. The server may alsogather analytical data from the aggregated performance data usingvarious tools. The client, on the other hand, may not have access to theperformance data. As such, the user of the client may have difficultyverifying that the remote service is providing the resources inaccordance with the prearranged set of operation conditions.

With cloud-based services, the applications may be delivered over aTransport Layer Security (TLS) or a Secure Sockets Layer (SSL)connection. Consequently, under existing techniques, networking-relatedmonitoring of the data flow from the client to the cloud-based servicemay lack the types of information available when the application waslocally installed. This may become problematic as application behaviormay vary from endpoint to endpoint. In addition, since currentencryption techniques may be unable to peer into the data flow betweenthe client and the cloud-based service, the network-related monitoringmay not be sufficient enough to detect and prevent information leakage.

To alleviate the technical drawbacks arising from moving an applicationfrom a self-hosted setup to a remote server, an embedded browser canintercept all communications for the application between the client andthe server. By intercepting the communications, the embedded browser maygather application telemetry data, such as HTTP message exchanges(including addresses, time, size, and status codes, etc.), processorusage, memory consumption, disk usage, and JavaScript engine statistics,among others. In addition, the application telemetry data may beaggregated on the client-side to create behavior profiles for anomalydetection. Furthermore, customer monitoring alerting mechanisms can beintegrated with the server-side analytics monitoring systems to create afeedback loop for the client-side application telemetry data monitoring.As the embedded browser is able to intercept all communications from theclient to the remote server, the embedded browser may use variouspattern recognition techniques to identify sensitive information and mayprevent the leakage of such information to the remote server.

In one aspect, the present disclosure is directed to a system and amethod for traffic inspection via embedded browsers. An applicationinspector module of an embedded browser executable on a client mayintercept network traffic for an application (e.g., SaaS application)served from a remote server. The application may be accessed via theembedded browser. The network traffic may include one or more packetsexchanged between the client and the remote server via a securecommunication channel. The application inspector module may identify acomputing resource usage on the client in executing the applicationaccessed via the embedded browser. The application inspector module maygenerate analytics data based on the intercepted network traffic and thecomputing resource usage. The application inspector module may maintaina user behavior profile based on the analytics data. The applicationinspector module may determine whether at least a portion of the networktraffic directed to the remote server contains sensitive information.Responsive to the determination, the application inspector module mayremove the portion of the network traffic containing the sensitiveinformation.

At least one aspect of the present disclosure is directed to a method ofmonitoring network applications. A client application on a client devicemay monitor traffic of a first network application hosted on a serverand at least one computing resource on the client device. The clientapplication may provide the client device with access to a plurality ofnetwork applications including the first network application via anembedded browser. The client application may generate analytics dataaccording to the monitored traffic of the first network application andthe monitored at least one computing resource on the client device. Theclient application may use, according to the generated analytics data, auser behavior model to identify anomalous activity associated with thefirst network application. The client application may restrict, inresponse to identifying the anomalous activity, access to the firstnetwork application.

In some embodiments, the client application may determine, using theuser behavior model, whether to restrict first data in the monitoredtraffic. In some embodiments, the client application may monitor thefirst data including one or more operations on the embedded browser. Insome embodiments, the client application may determine a deviationmeasure between the first data and expected data generated by the userbehavior model to determine whether to restrict the first data. Thedeviation measure may indicate a degree of anomalousness in the firstdata.

In some embodiments, monitoring the traffic may include monitoring thetraffic exchanged via a secure communications channel between the firstnetwork application hosted on the server and the client device. In someembodiments, monitoring the traffic may include monitoring the trafficoriginating from the client device providing access to the first networkapplication.

In some embodiments, generating the analytics data may include acquiringsecond analytics data from a telemetry tracker to combine with theanalytics data. The telemetry tracker may have visibility to the trafficoriginating from the server hosting the first network application. Insome embodiments, the analytics data may include at least one of acomputing resource performance metric, a network traffic performancemetric, and metadata.

In some embodiments, the client application may train the user behaviormodel using the analytics data. In some embodiments, the clientapplication may determine, via application of at least one policy,whether to restrict first data in the monitored traffic.

At least one aspect of the present disclosure is directed to a systemfor monitoring network applications. The system may include a clientapplication executable on one or more processors of a client device. Theclient application may monitor traffic of a first network applicationhosted on a server and at least one computing resource on the clientdevice. The client application may provide the client device with accessto a plurality of network applications including the first networkapplication via an embedded browser. The system may include an analyticstracking engine of the client application on the one or more processors.The analytics tracking engine may generate analytics data according tothe monitored traffic of the first network application and the monitoredat least one computing resource on the client device. The system mayinclude a behavior modeler engine of the client application executableon the one or more processors. The behavior modeler engine may use,according to the generated analytics data, a user behavior model toidentify anomalous activity associated with the first networkapplication. The client application may restrict, in response toidentifying the anomalous activity, access to the first networkapplication.

In some embodiments, the client application may determine, using theuser behavior model, whether to restrict first data in the monitoredtraffic. In some embodiments, the client application may monitor thefirst data including one or more operations on the embedded browser. Insome embodiments, the client application may determine a deviationmeasure between the first data and expected data generated by the userbehavior model to determine whether to restrict the first data. Thedeviation measure may indicate a degree of anomalousness in the firstdata.

In some embodiments, the analytics tracking engine may monitor thetraffic exchanged via a secure communications channel between the firstnetwork application hosted on the server and the client device. In someembodiments, the analytics tracking engine may monitor the trafficoriginating from the client device providing access to the first networkapplication.

In some embodiments, the analytics tracking engine may acquire secondanalytics data from a telemetry tracker to combine with the analyticsdata. The telemetry tracker may have visibility to the trafficoriginating from the server hosting the first network application. Insome embodiments, the analytics data may include at least one of acomputing resource performance metric, a network traffic performancemetric, and metadata.

In some embodiments, the client application may train the user behaviormodel using the analytics data. In some embodiments, the clientapplication may determine, via application of at least one policy,whether to restrict first data in the monitored traffic.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

Objects, aspects, features, and advantages of embodiments disclosedherein will become more fully apparent from the following detaileddescription, the appended claims, and the accompanying drawing figuresin which like reference numerals identify similar or identical elements.Reference numerals that are introduced in the specification inassociation with a drawing figure may be repeated in one or moresubsequent figures without additional description in the specificationin order to provide context for other features, and not every elementmay be labeled in every figure. The drawing figures are not necessarilyto scale, emphasis instead being placed upon illustrating embodiments,principles and concepts. The drawings are not intended to limit thescope of the claims included herewith.

FIG. 1 is a block diagram of embodiments of a computing device;

FIG. 2 is a block diagram of an illustrative embodiment of cloudservices for use in accessing resources;

FIG. 3 is a block diagram of an example embodiment of an enterprisemobility management system;

FIG. 4 is a block diagram of a system of an embedded browser;

FIG. 5 is a block diagram of an example embodiment of a system for usinga secure browser;

FIG. 6 is an example representation of an implementation for browserredirection using a secure browser plug-in;

FIG. 7 is a block diagram of example embodiment of a system of using asecure browser;

FIG. 8 is a block diagram of an example embodiment of a system for usinglocal embedded browser(s) and hosted secured browser(s);

FIG. 9 is an example process flow for using local embedded browser(s)and hosted secured browser(s);

FIG. 10 is an example embodiment of an example embodiment of a systemfor managing user access to webpages;

FIG. 11 is a block diagram of an example embodiment of a system forinspecting traffic of a client application accessing resources ofnetwork applications;

FIG. 12 is a process diagram of an example embodiment of a system forgathering analytics for the traffic of a client application accessingresources;

FIG. 13A-C are process diagrams of example embodiments of a system forcontrolling traffic from a client application;

FIG. 14 is a flow diagram of an example embodiment of a method forinspecting traffic of a client application accessing resources ofnetwork applications; and

FIG. 15 is a flow diagram of an example embodiment of a method ofmonitoring network applications.

DETAILED DESCRIPTION

For purposes of reading the description of the various embodimentsbelow, the following descriptions of the sections of the specificationand their respective contents may be helpful:

Section A describes a computing environment which may be useful forpracticing embodiments described herein;

Section B describes systems and methods for an embedded browser.

Section C describes embodiments of systems and methods for trafficinspection via embedded browsers.

A. Computing Environment

Prior to discussing the specifics of embodiments of the systems andmethods detailed herein in Section B, it may be helpful to discuss thecomputing environments in which such embodiments may be deployed.

As shown in FIG. 1, computer 101 may include one or more processors 103,volatile memory 122 (e.g., random access memory (RAM)), non-volatilememory 128 (e.g., one or more hard disk drives (HDDs) or other magneticor optical storage media, one or more solid state drives (SSDs) such asa flash drive or other solid state storage media, one or more hybridmagnetic and solid state drives, and/or one or more virtual storagevolumes, such as a cloud storage, or a combination of such physicalstorage volumes and virtual storage volumes or arrays thereof), userinterface (UI) 123, one or more communications interfaces 118, andcommunication bus 150. User interface 123 may include graphical userinterface (GUI) 124 (e.g., a touchscreen, a display, etc.) and one ormore input/output (I/O) devices 126 (e.g., a mouse, a keyboard, amicrophone, one or more speakers, one or more cameras, one or morebiometric scanners, one or more environmental sensors, one or moreaccelerometers, etc.). Non-volatile memory 128 stores operating system115, one or more applications 116, and data 117 such that, for example,computer instructions of operating system 115 and/or applications 116are executed by processor(s) 103 out of volatile memory 122. In someembodiments, volatile memory 122 may include one or more types of RAMand/or a cache memory that may offer a faster response time than a mainmemory. Data may be entered using an input device of GUI 124 or receivedfrom I/O device(s) 126. Various elements of computer 101 may communicatevia one or more communication buses, shown as communication bus 150.

Computer 101 as shown in FIG. 1 is shown merely as an example, asclients, servers, intermediary and other networking devices and may beimplemented by any computing or processing environment and with any typeof machine or set of machines that may have suitable hardware and/orsoftware capable of operating as described herein. Processor(s) 103 maybe implemented by one or more programmable processors to execute one ormore executable instructions, such as a computer program, to perform thefunctions of the system. As used herein, the term “processor” describescircuitry that performs a function, an operation, or a sequence ofoperations. The function, operation, or sequence of operations may behard coded into the circuitry or soft coded by way of instructions heldin a memory device and executed by the circuitry. A “processor” mayperform the function, operation, or sequence of operations using digitalvalues and/or using analog signals. In some embodiments, the “processor”can be embodied in one or more application specific integrated circuits(ASICs), microprocessors, digital signal processors (DSPs), graphicsprocessing units (GPUs), microcontrollers, field programmable gatearrays (FPGAs), programmable logic arrays (PLAs), multi-core processors,or general-purpose computers with associated memory. The “processor” maybe analog, digital or mixed-signal. In some embodiments, the “processor”may be one or more physical processors or one or more “virtual” (e.g.,remotely located or “cloud”) processors. A processor including multipleprocessor cores and/or multiple processors multiple processors mayprovide functionality for parallel, simultaneous execution ofinstructions or for parallel, simultaneous execution of one instructionon more than one piece of data.

Communications interfaces 118 may include one or more interfaces toenable computer 101 to access a computer network such as a Local AreaNetwork (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN),or the Internet through a variety of wired and/or wireless or cellularconnections.

In described embodiments, the computing device 101 may execute anapplication on behalf of a user of a client computing device. Forexample, the computing device 101 may execute a virtual machine, whichprovides an execution session within which applications execute onbehalf of a user or a client computing device, such as a hosted desktopsession. The computing device 101 may also execute a terminal servicessession to provide a hosted desktop environment. The computing device101 may provide access to a computing environment including one or moreof: one or more applications, one or more desktop applications, and oneor more desktop sessions in which one or more applications may execute.

B. Systems and Methods for an Embedded Browser

The present disclosure is directed towards systems and methods of anembedded browser. A client application executing on a client device canallow a user to access applications (apps) that are served from and/orhosted on one or more servers, such as web applications andsoftware-as-a-service (SaaS) applications (hereafter sometimes generallyreferred to as network applications). A browser that is embedded orintegrated with the client application can render to the user a networkapplication that is accessed or requested via the client application,and can enable interactivity between the user and the networkapplication. The browser is sometimes referred to as an embeddedbrowser, and the client application with embedded browser (CEB) issometimes referred to as a workspace application. The client applicationcan establish a secure connection to the one or more servers to providean application session for the user to access the network applicationusing the client device and the embedded browser. The embedded browsercan be integrated with the client application to ensure that trafficrelated to the network application is routed through and/or processed inthe client application, which can provide the client application withreal-time visibility to the traffic (e.g., when decrypted through theclient application), and user interactions and behavior. The embeddedbrowser can provide a seamless experience to a user as the networkapplication is requested via the user interface (shared by the clientapplication and the embedded browser) and rendered through the embeddedbrowser within the same user interface.

The client application can terminate one end of a secured connectionestablished with a server of a network application, such as a securesockets layer (SSL) virtual private network (VPN) connection. The clientapplication can receive encrypted traffic from the network application,and can decrypt the traffic before further processing (e.g., renderingby the embedded browser). The client application can monitor thereceived traffic (e.g., in encrypted packet form), and also have fullvisibility into the decrypted data stream and/or the SSL stack. Thisvisibility can allow the client application to perform or facilitatepolicy-based management (e.g., including data loss prevention (DLP)capabilities), application control (e.g., to improve performance,service level), and collection and production of analytics. Forinstance, the local CEB can provide an information technology (IT)administrator with a controlled system for deploying web and SaaSapplications through the CEB, and allow the IT administrator to setpolicies or configurations via the CEB for performing any of theforgoing activities.

Many web and SaaS delivered applications connect from web servers togeneric browsers (e.g., Internet Explorer, Firefox, and so on) of users.Once authenticated, the entire session of such a network application isencrypted. However, in this scenario, an administrator may not havevisibility, analytics, or control of the content entering the networkapplication from the user's digital workspace, or the content leavingthe network application and entering the user's digital workspace.Moreover, content of a network application viewed in a generic browsercan be copied or downloaded (e.g., by a user or program) to potentiallyany arbitrary application or device, resulting in a possible breach indata security.

This present systems and methods can ensure that traffic associated witha network application is channeled through a CEB. By way ofillustration, when a user accesses a SaaS web service with securityassertion markup language (SAML) enabled for instance, the correspondingaccess request can be forwarded to a designated gateway service thatdetermines, checks or verifies if the CEB was used to make the accessrequest. Responsive to determining that a CEB was used to make theaccess request, the gateway service can perform or provideauthentication and single-sign-on (SSO), and can allow the CEB toconnect directly to the SaaS web service. Encryption (e.g., standardencryption) can be used for the application session between the CEB andthe SaaS web service. When the content from the web service isunencrypted in the CEB to the viewed via the embedded browser, and/orwhen input is entered via the CEB, the CEB can provide added services onselective application-related information for control and analytics forinstance. For example, an analytics agent or application programminginterface (API) can be embedded in the CEB to provide or perform theadded services.

The CEB (sometimes referred to as workspace application or receiver) caninteroperate with one or more gateway services, intermediaries and/ornetwork servers (sometimes collectively referred to as cloud services orCitrix Cloud) to provide access to a network application. Features andelements of an environment related to the operation of an embodiment ofcloud services are described below.

FIG. 2 illustrates an embodiment of cloud services for use in accessingresources including network applications. The cloud services can includean enterprise mobility technical architecture 200, which can include anaccess gateway 260 in one illustrative embodiment. The architecture canbe used in a bring-your-own-device (BYOD) environment for instance. Thearchitecture can enable a user of a client device 204 (e.g., a mobile orother device) to both access enterprise or personal resources from aclient device 202, and use the client device 204 for personal use. Theuser may access such enterprise resources 204 or enterprise services 208via a client application executing on the client device 204. The usermay access such enterprise resources 204 or enterprise services 208using a client device 204 that is purchased by the user or a clientdevice 202 that is provided by the enterprise to user. The user mayutilize the client device 202 for business use only or for business andpersonal use. The client device may run an iOS operating system, andAndroid operating system, or the like. The enterprise may choose toimplement policies to manage the client device 204. The policies may beimplemented through a firewall or gateway in such a way that the clientdevice may be identified, secured or security verified, and providedselective or full access to the enterprise resources. The policies maybe client device management policies, mobile application managementpolicies, mobile data management policies, or some combination of clientdevice, application, and data management policies. A client device 204that is managed through the application of client device managementpolicies may be referred to as an enrolled device. The client devicemanagement policies can be applied via the client application forinstance.

In some embodiments, the operating system of the client device may beseparated into a managed partition 210 and an unmanaged partition 212.The managed partition 210 may have policies applied to it to secure theapplications running on and data stored in the managed partition. Theapplications running on the managed partition may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the client device management system when that application isexecuting on the device. By operating in accordance with theirrespective policy file(s), each application may be allowed or restrictedfrom communications with one or more other applications and/orresources, thereby creating a virtual partition. Thus, as used herein, apartition may refer to a physically partitioned portion of memory(physical partition), a logically partitioned portion of memory (logicalpartition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapps as described herein (virtual partition). Stated differently, byenforcing policies on managed apps, those apps may be restricted to onlybe able to communicate with other managed apps and trusted enterpriseresources, thereby creating a virtual partition that is not accessibleby unmanaged apps and devices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The client applicationcan include a secure application launcher 218. The secure applicationsmay be secure native applications 214, secure remote applications 222executed by the secure application launcher 218, virtualizationapplications 226 executed by the secure application launcher 218, andthe like. The secure native applications 214 may be wrapped by a secureapplication wrapper 220. The secure application wrapper 220 may includeintegrated policies that are executed on the client device 202 when thesecure native application is executed on the device. The secureapplication wrapper 220 may include meta-data that points the securenative application 214 running on the client device 202 to the resourceshosted at the enterprise that the secure native application 214 mayrequire to complete the task requested upon execution of the securenative application 214. The secure remote applications 222 executed by asecure application launcher 218 may be executed within the secureapplication launcher application 218. The virtualization applications226 executed by a secure application launcher 218 may utilize resourceson the client device 202, at the enterprise resources 204, and the like.The resources used on the client device 202 by the virtualizationapplications 226 executed by a secure application launcher 218 mayinclude user interaction resources, processing resources, and the like.The user interaction resources may be used to collect and transmitkeyboard input, mouse input, camera input, tactile input, audio input,visual input, gesture input, and the like. The processing resources maybe used to present a user interface, process data received from theenterprise resources 204, and the like. The resources used at theenterprise resources 204 by the virtualization applications 226 executedby a secure application launcher 218 may include user interfacegeneration resources, processing resources, and the like. The userinterface generation resources may be used to assemble a user interface,modify a user interface, refresh a user interface, and the like. Theprocessing resources may be used to create information, readinformation, update information, delete information, and the like. Forexample, the virtualization application may record user interactionsassociated with a graphical user interface (GUI) and communicate them toa server application where the server application may use the userinteraction data as an input to the application operating on the server.In this arrangement, an enterprise may elect to maintain the applicationon the server side as well as data, files, etc., associated with theapplication. While an enterprise may elect to “mobilize” someapplications in accordance with the principles herein by securing themfor deployment on the client device (e.g., via the client application),this arrangement may also be elected for certain applications. Forexample, while some applications may be secured for use on the clientdevice, others might not be prepared or appropriate for deployment onthe client device so the enterprise may elect to provide the mobile useraccess to the unprepared applications through virtualization techniques.As another example, the enterprise may have large complex applicationswith large and complex data sets (e.g., material resource planningapplications) where it would be very difficult, or otherwiseundesirable, to customize the application for the client device so theenterprise may elect to provide access to the application throughvirtualization techniques. As yet another example, the enterprise mayhave an application that maintains highly secured data (e.g., humanresources data, customer data, engineering data) that may be deemed bythe enterprise as too sensitive for even the secured mobile environmentso the enterprise may elect to use virtualization techniques to permitmobile access to such applications and data. An enterprise may elect toprovide both fully secured and fully functional applications on theclient device. The enterprise can use a client application, which caninclude a virtualization application, to allow access to applicationsthat are deemed more properly operated on the server side. In anembodiment, the virtualization application may store some data, files,etc., on the mobile phone in one of the secure storage locations. Anenterprise, for example, may elect to allow certain information to bestored on the phone while not permitting other information.

In connection with the virtualization application, as described herein,the client device may have a virtualization application that is designedto present GUIs and then record user interactions with the GUI. Thevirtualization application may communicate the user interactions to theserver side to be used by the server side application as userinteractions with the application. In response, the application on theserver side may transmit back to the client device a new GUI. Forexample, the new GUI may be a static page, a dynamic page, an animation,or the like, thereby providing access to remotely located resources.

The secure applications may access data stored in a secure datacontainer 228 in the managed partition 210 of the client device. Thedata secured in the secure data container may be accessed by the securewrapped applications 214, applications executed by a secure applicationlauncher 222, virtualization applications 226 executed by a secureapplication launcher 218, and the like. The data stored in the securedata container 228 may include files, databases, and the like. The datastored in the secure data container 228 may include data restricted to aspecific secure application 230, shared among secure applications 232,and the like. Data restricted to a secure application may include securegeneral data 234 and highly secure data 238. Secure general data may usea strong form of encryption such as Advanced Encryption Standard (AES)128-bit encryption or the like, while highly secure data 238 may use avery strong form of encryption such as AES 256-bit encryption. Datastored in the secure data container 228 may be deleted from the deviceupon receipt of a command from the device manager 224. The secureapplications may have a dual-mode option 240. The dual mode option 240may present the user with an option to operate the secured applicationin an unsecured or unmanaged mode. In an unsecured or unmanaged mode,the secure applications may access data stored in an unsecured datacontainer 242 on the unmanaged partition 212 of the client device 202.The data stored in an unsecured data container may be personal data 244.The data stored in an unsecured data container 242 may also be accessedby unsecured applications 248 that are running on the unmanagedpartition 212 of the client device 202. The data stored in an unsecureddata container 242 may remain on the client device 202 when the datastored in the secure data container 228 is deleted from the clientdevice 202. An enterprise may want to delete from the client deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The client device 202 may connect to enterprise resources 204 andenterprise services 208 at an enterprise, to the public Internet 248,and the like. The client device may connect to enterprise resources 204and enterprise services 208 through virtual private network connections.The virtual private network connections, also referred to as microVPN orapplication-specific VPN, may be specific to particular applications(e.g., as illustrated by microVPNs 250), particular devices, particularsecured areas on the client device (e.g., as illustrated by O/S VPN252), and the like. For example, each of the wrapped applications in thesecured area of the phone may access enterprise resources through anapplication specific VPN such that access to the VPN would be grantedbased on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP)traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, applicationmanagement traffic, and the like. The virtual private networkconnections may support and enable single-sign-on authenticationprocesses 254. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 258. The authentication service 258 may thengrant to the user access to multiple enterprise resources 204, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 204.

The virtual private network connections may be established and managedby an access gateway 260. The access gateway 260 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 204 to the client device 202. The access gatewaymay also re-route traffic from the client device 202 to the publicInternet 248, enabling the client device 202 to access publiclyavailable and unsecured applications that run on the public Internet248. The client device may connect to the access gateway via a transportnetwork 262. The transport network 262 may use one or more transportprotocols and may be a wired network, wireless network, cloud network,local area network, metropolitan area network, wide area network, publicnetwork, private network, and the like.

The enterprise resources 204 may include email servers, file sharingservers, SaaS/Web applications, Web application servers, Windowsapplication servers, and the like. Email servers may include Exchangeservers, Lotus Notes servers, and the like. File sharing servers mayinclude ShareFile servers, and the like. SaaS applications may includeSalesforce, and the like. Windows application servers may include anyapplication server that is built to provide applications that areintended to run on a local Windows operating system, and the like. Theenterprise resources 204 may be premise-based resources, cloud basedresources, and the like. The enterprise resources 204 may be accessed bythe client device 202 directly or through the access gateway 260. Theenterprise resources 204 may be accessed by the client device 202 via atransport network 262. The transport network 262 may be a wired network,wireless network, cloud network, local area network, metropolitan areanetwork, wide area network, public network, private network, and thelike.

Cloud services can include an access gateway 260 and/or enterpriseservices 208. The enterprise services 208 may include authenticationservices 258, threat detection services 264, device manager services224, file sharing services 268, policy manager services 270, socialintegration services 272, application controller services 274, and thelike. Authentication services 258 may include user authenticationservices, device authentication services, application authenticationservices, data authentication services and the like. Authenticationservices 258 may use certificates. The certificates may be stored on theclient device 202, by the enterprise resources 204, and the like. Thecertificates stored on the client device 202 may be stored in anencrypted location on the client device. The certificate may betemporarily stored on the client device 202 for use at the time ofauthentication, and the like. Threat detection services 264 may includeintrusion detection services, unauthorized access attempt detectionservices, and the like. Unauthorized access attempt detection servicesmay include unauthorized attempts to access devices, applications, data,and the like. Device management services 224 may include configuration,provisioning, security, support, monitoring, reporting, anddecommissioning services. File sharing services 268 may include filemanagement services, file storage services, file collaboration services,and the like. Policy manager services 270 may include device policymanager services, application policy manager services, data policymanager services, and the like. Social integration services 272 mayinclude contact integration services, collaboration services,integration with social networks such as Facebook, Twitter, andLinkedIn, and the like. Application controller services 274 may includemanagement services, provisioning services, deployment services,assignment services, revocation services, wrapping services, and thelike.

The enterprise mobility technical architecture 200 may include anapplication store 278. The application store 278 may include unwrappedapplications 280, pre-wrapped applications 282, and the like.Applications may be populated in the application store 278 from theapplication controller 274. The application store 278 may be accessed bythe client device 202 through the access gateway 260, through the publicInternet 248, or the like. The application store may be provided with anintuitive and easy to use User Interface.

A software development kit 284 may provide a user the capability tosecure applications selected by the user by providing a secure wrapperaround the application. An application that has been wrapped using thesoftware development kit 284 may then be made available to the clientdevice 202 by populating it in the application store 278 using theapplication controller 274.

The enterprise mobility technical architecture 200 may include amanagement and analytics capability. The management and analyticscapability may provide information related to how resources are used,how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 3 depicts is an illustrative embodiment of an enterprise mobilitymanagement system 300. Some of the components of the mobility managementsystem 200 described above with reference to FIG. 2 have been omittedfor the sake of simplicity. The architecture of the system 300 depictedin FIG. 3 is similar in many respects to the architecture of the system200 described above with reference to FIG. 2 and may include additionalfeatures not mentioned above.

In this case, the left hand side represents an enrolled client device302 with a client agent 304, which interacts with gateway server 306 toaccess various enterprise resources 308 and services 309 such as Web orSasS applications, Exchange, Sharepoint, public-key infrastructure (PKI)Resources, Kerberos Resources, Certificate Issuance service, as shown onthe right hand side above. The gateway server 306 can includeembodiments of features and functionalities of the cloud services, suchas access gateway 260 and application controller functionality. Althoughnot specifically shown, the client agent 304 may be part of, and/orinteract with the client application which can operate as an enterpriseapplication store (storefront) for the selection and/or downloading ofnetwork applications.

The client agent 304 can act as a UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the High-Definition User Experience (HDX) or IndependentComputing Architecture (ICA) display remoting protocol. The client agent304 can also support the installation and management of nativeapplications on the client device 302, such as native iOS or Androidapplications. For example, the managed applications 310 (mail, browser,wrapped application) shown in the figure above are native applicationsthat execute locally on the device. Client agent 304 and applicationmanagement framework of this architecture act to provide policy drivenmanagement capabilities and features such as connectivity and SSO(single sign on) to enterprise resources/services 308. The client agent304 handles primary user authentication to the enterprise, for instanceto access gateway (AG) with SSO to other gateway server components. Theclient agent 304 obtains policies from gateway server 306 to control thebehavior of the managed applications 310 on the client device 302.

The Secure interprocess communication (IPC) links 312 between the nativeapplications 310 and client agent 304 represent a management channel,which allows client agent to supply policies to be enforced by theapplication management framework 314 “wrapping” each application. TheIPC channel 312 also allows client agent 304 to supply credential andauthentication information that enables connectivity and SSO toenterprise resources 308. Finally, the IPC channel 312 allows theapplication management framework 314 to invoke user interface functionsimplemented by client agent 304, such as online and offlineauthentication.

Communications between the client agent 304 and gateway server 306 areessentially an extension of the management channel from the applicationmanagement framework 314 wrapping each native managed application 310.The application management framework 314 requests policy informationfrom client agent 304, which in turn requests it from gateway server306. The application management framework 314 requests authentication,and client agent 304 logs into the gateway services part of gatewayserver 306 (also known as NetScaler access gateway). Client agent 304may also call supporting services on gateway server 306, which mayproduce input material to derive encryption keys for the local datavaults 316, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the application management framework 314 “wraps” eachmanaged application 310. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 314 may “pair” with client agent 304 on first launch of anapplication 310 to initialize the Secure IPC channel and obtain thepolicy for that application. The application management framework 314may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the application 310.

The application management framework 314 may use services provided byclient agent 304 over the Secure IPC channel 312 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 316 (containers) may be also managed byappropriate interactions between the managed applications 310 and clientagent 304. Vaults 316 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 316 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 310 through access gateway 306. The applicationmanagement framework 314 is responsible for orchestrating the networkaccess on behalf of each application 310. Client agent 304 mayfacilitate these network connections by providing suitable time limitedsecondary credentials obtained following online authentication. Multiplemodes of network connection may be used, such as reverse web proxyconnections and end-to-end VPN-style tunnels 318.

The Mail and Browser managed applications 310 can have special statusand may make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAG logon. The Browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture can support the incorporation of various othersecurity features. For example, gateway server 306 (including itsgateway services) in some cases might not need to validate activedirectory (AD) passwords. It can be left to the discretion of anenterprise whether an AD password is used as an authentication factorfor some users in some situations. Different authentication methods maybe used if a user is online or offline (i.e., connected or not connectedto a network).

Step up authentication is a feature wherein gateway server 306 mayidentify managed native applications 310 that are allowed to have accessto more sensitive data using strong authentication, and ensure thataccess to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequested from the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 316 (containers) on the client device 302. The vaults 316 may beencrypted so that all on-device data including clipboard/cache data,files, databases, and configurations are protected. For on-line vaults,the keys may be stored on the server (gateway server 306), and foroff-line vaults, a local copy of the keys may be protected by a userpassword or biometric validation. When data is stored locally on thedevice 302 in the secure container 316, it is preferred that a minimumof AES 256 encryption algorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 310 are logged and reported to the backend. Datawiping may be supported, such as if the application 310 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase or biometric data supplied by the user (ifoffline access is required). It may be XORed with another key randomlygenerated and stored on the server side if offline access is notrequired. Key Derivation functions may operate such that keys generatedfrom the user password use KDFs (key derivation functions, notablyPassword-Based Key Derivation Function 2 (PBKDF2)) rather than creatinga cryptographic hash of it. The latter makes a key susceptible to bruteforce or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector might cause multiple copies of thesame encrypted data to yield different cipher text output, preventingboth replay and cryptanalytic attacks. This may also prevent an attackerfrom decrypting any data even with a stolen encryption key. Further,authentication then decryption may be used, wherein application data isdecrypted only after the user has authenticated within the application.Another feature may relate to sensitive data in memory, which may bekept in memory (and not in disk) only when it is needed. For example,login credentials may be wiped from memory after login, and encryptionkeys and other data inside objective-C instance variables are notstored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented via the CEB, wherein after apolicy-defined period of inactivity, a user session is terminated.

Data leakage from the application management framework 314 may beprevented in other ways. For example, when an application 310 is put inthe background, the memory may be cleared after a predetermined(configurable) time period. When backgrounded, a snapshot may be takenof the last displayed screen of the application to fasten theforegrounding process. The screenshot may contain confidential data andhence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 320 without the use of an AD (active directory) 322 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 320 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 320. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 310 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want storefront to be accessed inthis manner. In this case, the client agent 304 may require the user toset a custom offline password and the AD password is not used. Gatewayserver 306 may provide policies to control and enforce passwordstandards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 310 as secondary credentials (for the purposeof accessing PKI protected web resources via the application managementframework micro VPN feature). For example, an application may utilizesuch a certificate. In this case, certificate-based authentication usingActiveSync protocol may be supported, wherein a certificate from theclient agent 304 may be retrieved by gateway server 306 and used in akeychain. Each managed application may have one associated clientcertificate, identified by a label that is defined in gateway server306.

Gateway server 306 may interact with an Enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 304 and the application management framework 314 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications, and ultimately by arbitrarywrapped applications (provided those applications use web service stylecommunication patterns where it is reasonable for the applicationmanagement framework to mediate https requests).

Application management client certificate support on iOS may rely onimporting a public-key cryptography standards (PKCS) 12 BLOB (BinaryLarge Object) into the iOS keychain in each managed application for eachperiod of use. Application management framework client certificatesupport may use a HTTPS implementation with private in-memory keystorage. The client certificate might never be present in the iOSkeychain and might not be persisted except potentially in “online-only”data value that is strongly protected.

Mutual SSL or TLS may also be implemented to provide additional securityby requiring that a client device 302 is authenticated to theenterprise, and vice versa. Virtual smart cards for authentication togateway server 306 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toActive Directory (AD) 322, using an AD password or trusted clientcertificate, and obtain Kerberos service tickets to respond to HTTPNegotiate authentication challenges. The limited support feature relatesto constrained delegation in Citrix Access Gateway Enterprise Edition(AGEE), where AGEE supports invoking Kerberos protocol transition so itcan obtain and use Kerberos service tickets (subject to constraineddelegation) in response to HTTP Negotiate authentication challenges.This mechanism works in reverse web proxy (aka corporate virtual privatenetwork (CVPN)) mode, and when http (but not https) connections areproxied in VPN and MicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when an application 310 is not running.

A multi-site architecture or configuration of enterprise applicationstore and an application controller may be supported that allows usersto be service from one of several different locations in case offailure.

In some cases, managed applications 310 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 310 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is used, when an application reads a certificate for“who am I,” when an application uses the certificate to build a securesession token, and when an application uses private keys for digitalsigning of important data (e.g., transaction log) or for temporary dataencryption.

Referring now to FIG. 4, depicted is a block diagram of a system 400 ofan embedded browser. In brief overview, the system 400 may include aclient device 402 with a digital workspace for a user, a clientapplication 404, cloud services 408 operating on at least one networkdevice 432, and network applications 406 served from and/or hosted onone or more servers 430. The client application 404 can for instanceinclude at least one of: an embedded browser 410, a networking agent412, a cloud services agent 414, a remote session agent 416, or a securecontainer 418. The cloud services 408 can for instance include at leastone of: secure browser(s) 420, an access gateway 422 (or CIS, e.g., forregistering and/or authenticating the client application and/or user),or analytics services 424 (or CAS, e.g., for receiving information fromthe client application for analytics). The network applications 406 caninclude sanctioned applications 426 and non-sanctioned applications 428.

Each of the above-mentioned elements or entities is implemented inhardware, or a combination of hardware and software, in one or moreembodiments. Each component of the system 200 may be implemented usinghardware or a combination of hardware or software detailed above inconnection with FIG. 1. For instance, each of these elements or entitiescan include any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of the client device 402, the at least one network device 432and/or the one or more servers 430. The hardware includes circuitry suchas one or more processors in one or more embodiments. For example, theat least one network device 432 and/or the one or more servers 430 caninclude any of the elements of a computing device described above inconnection with at least FIG. 1 for instance.

The client device 402 can include any embodiment of a computing devicedescribed above in connection with at least FIG. 1 for instance. Theclient device 402 can include any user device such as a desktopcomputer, a laptop computer, a tablet device, a smart phone, or anyother mobile or personal device. The client device 402 can include adigital workspace of a user, which can include file system(s), cache ormemory (e.g., including electronic clipboard(s)), container(s),application(s) and/or other resources on the client device 402. Thedigital workspace can include or extend to one or more networksaccessible by the client device 402, such as an intranet and theInternet, including file system(s) and/or other resources accessible viathe one or more networks. A portion of the digital workspace can besecured via the use of the client application 404 with embedded browser410 (CEB) for instance. The secure portion of the digital workspace caninclude for instance file system(s), cache or memory (e.g., includingelectronic clipboard(s)), application(s), container(s) and/or otherresources allocated to the CEB, and/or allocated by the CEB to networkapplication(s) 406 accessed via the CEB. The secure portion of thedigital workspace can also include resources specified by the CEB (viaone or more policies) for inclusion in the secure portion of the digitalworkspace (e.g., a particular local application can be specified via apolicy to be allowed to receive data obtained from a networkapplication).

The client application 404 can include one or more components, such asan embedded browser 410, a networking agent 412, a cloud services agent414 (sometimes referred to as management agent), a remote session agent416 (sometimes referred to as HDX engine), and/or a secure container 418(sometimes referred to as secure cache container). One or more of thecomponents can be installed as part of a software build or release ofthe client application 404 or CEB, or separately acquired or downloadedand installed/integrated into an existing installation of the clientapplication 404 or CEB for instance. For instance, the client device maydownload or otherwise receive the client application 404 (or anycomponent) from the network device(s) 432. In some embodiments, theclient device may send a request for the client application 404 to thenetwork device(s) 432. For example, a user of the client device caninitiate a request, download and/or installation of the clientapplication. The network device(s) 432 in turn may send the clientapplication to the client device. In some embodiments, the networkdevice(s) 432 may send a setup or installation application for theclient application to the client device. Upon receipt, the client devicemay install the client application onto a hard disk of the clientdevice. In some embodiments, the client device may run the setupapplication to unpack or decompress a package of the client application.In some embodiments, the client application may be an extension (e.g.,an add-on, an add-in, an applet or a plug-in) to another application(e.g., a networking agent 414) installed on the client device. Theclient device may install the client application to interface orinter-operate with the pre-installed application. In some embodiments,the client application may be a standalone application. The clientdevice may install the client application to execute as a separateprocess.

The embedded browser 410 can include elements and functionalities of aweb browser application or engine. The embedded browser 410 can locallyrender network application(s) as a component or extension of the clientapplication. For instance, the embedded browser 410 can render aSaaS/Web application inside the CEB which can provide the CEB with fullvisibility and control of the application session. The embedded browsercan be embedded or incorporated into the client application via anymeans, such as direct integration (e.g., programming language or scriptinsertion) into the executable code of the client application, or viaplugin installation. For example, the embedded browser can include aChromium based browser engine or other type of browser engine, that canbe embedded into the client application, using the Chromium embeddedframework (CEF) for instance. The embedded browser can include aHTML5-based layout graphical user interface (GUI). The embedded browsercan provide HTML rendering and JavaScript support to a clientapplication incorporating various programming languages. For example,elements of the embedded browser can bind to a client applicationincorporating C, C++, Delphi, Go, Java, .NET/Mono, Visual Basic 6.0,and/or Python.

In some embodiments, the embedded browser comprises a plug-in installedon the client application. For example, the plug-in can include one ormore components. One such components can be an ActiveX control or Javacontrol or any other type and/or form of executable instructions capableof loading into and executing in the client application. For example,the client application can load and run an Active X control of theembedded browser, such as in a memory space or context of the clientapplication. In some embodiments, the embedded browser can be installedas an extension on the client application, and a user can choose toenable or disable the plugin or extension. The embedded browser (e.g.,via the plugin or extension) can form or operate as a secured browserfor securing, using and/or accessing resources within the securedportion of the digital workspace.

The embedded browser can incorporate code and functionalities beyondthat available or possible in a standard or typical browser. Forinstance, the embedded browser can bind with or be assigned with asecured container 418, to define at least part of the secured portion ofa user's digital workspace. The embedded browser can bind with or beassigned with a portion of the client device's cache to form a securedclipboard (e.g., local to the client device, or extendable to otherdevices), that can be at least part of the secured container 418. Theembedded browser can be integrated with the client application to ensurethat traffic related to network applications is routed through and/orprocessed in the client application, which can provide the clientapplication with real-time visibility to the traffic (e.g., whendecrypted through the client application). This visibility to thetraffic can allow the client application to perform or facilitatepolicy-based management (e.g., including data loss prevention (DLP)capabilities), application control, and collection and production ofanalytics.

In some embodiments, the embedded browser incorporates one or more othercomponents of the client application 404, such as the cloud servicesagent 414, remote session agent 416 and/or secure container 418. Forinstance, a user can use the cloud services agent 414 of the embeddedbrowser to interoperate with the access gateway 422 (sometimes referredto as CIS) to access a network application. For example, the cloudservices agent 414 can execute within the embedded browser, and canreceive and transmit navigation commands from the embedded browser to ahosted network application. The cloud services agent can use a remotepresentation protocol to display the output generated by the networkapplication to the embedded browser. For example, the cloud servicesagent 414 can include a HTML5 web client that allows end users to accessremote desktops and/or applications on the embedded browser.

The client application 404 and CEB operates on the application layer ofthe operational (OSI) stack of the client device. The client application404 can include and/or execute one or more agents that interoperate withthe cloud services 408.

For example, the cloud services agent 414 can convey or feed informationto analytics services 424 of the cloud services 408, such as informationabout SaaS interaction events visible to the CEB. Such a configurationusing the CEB can monitor or capture information for analytics withouthaving an inline device or proxy located between the client device andthe server(s) 430, or using a SaaS API gateway ‘out-of-band’ approach.In some embodiments, the cloud services agent 414 does not executewithin the embedded browser. In these embodiments, a user can similarlyuse the cloud services agent 414 to interoperate with the access gateway(or CIS) 422 to access a network application. For instance, the cloudservices agent 414 can register and/or authenticate with the accessgateway (or CIS) 422, and can obtain a list of the network applicationsfrom the access gateway (or CIS) 422. The cloud services agent 414 caninclude and/or operate as an application store (or storefront) for userselection and/or downloading of network applications. Upon logging in toaccess a network application, the cloud services agent 414 can interceptand transmit navigation commands from the embedded browser to thenetwork application. The cloud services agent can use a remotepresentation protocol to display the output generated by the networkapplication to the embedded browser. For example, the cloud servicesagent 414 can include a HTML5 web client that allows end users to accessremote desktops and/or applications on the embedded browser.

In some embodiments, the cloud services agent 414 provides single signon (SSO) capability for the user and/or client device to access aplurality of network applications. The cloud services agent 414 canperform user authentication to access network applications as well asother network resources and services, by communicating with the accessgateway 422 for instance. For example, the cloud services agent 414 canauthenticate or register with the access gateway 422, to access othercomponents of the cloud services 408 and/or the network applications406. Responsive to the authentication or registration, the accessgateway 422 can perform authentication and/or SSO for (or on behalf of)the user and/or client application, with the network applications.

In some embodiments, the cloud services agent 414 provides policy drivenmanagement capabilities and features related to the use and/or access ofnetwork applications. For example, the cloud services agent 414 caninclude a policy engine to apply one or more policies to determineaccess control and/or connectivity to resources such as networkapplications. When a session is established between the clientapplication and a server 430 providing a SaaS application for instance,the cloud services agent 414 can apply one or more policies to controltraffic levels and/or traffic types (or other aspects) of the session,for instance to manage a service level of the SaaS application.Additional aspects of the application traffic that can be controlled ormanaged can include encryption level and/or encryption type applied tothe traffic, level of interactivity allowed for a user, limited accessto certain features of the network application (e.g., print-screen,save, edit or copy functions), restrictions to use or transfer of dataobtained from the network application, limit concurrent access to two ormore network applications, limit access to certain file repositories orother resources, and so on.

The client application 404 can include a networking agent 412. Thenetworking agent 412 is sometimes referred to as a software-defined widearea network (SD-WAN) agent, mVPN agent, or microVPN agent. Thenetworking agent 412 can establish or facilitate establishment of anetwork connection between the client application and one or moreresources (e.g., server 430 serving a network application). Thenetworking agent 412 can perform handshaking for a requested connectionfrom the client application to access a network application, and canestablish the requested connection (e.g., secure or encryptedconnection). The networking agent 412 can connect to enterpriseresources (including services) for instance via a virtual privatenetwork (VPN). For example, the networking agent 412 can establish asecure socket layer (SSL) VPN between the client application and aserver 430 providing the network application 406. The VPN connections,sometimes referred to as microVPN or application-specific VPN, may bespecific to particular network applications, particular devices,particular secured areas on the client device, and the like, forinstance as discussed above in connection with FIG. 3. Such VPNconnections can carry Microsoft Exchange traffic, Microsoft ActiveDirectory traffic, HyperText Transfer Protocol (HTTP) traffic, HyperTextTransfer Protocol Secure (HTTPS) traffic, as some examples.

The remote session agent 416 (sometimes referred to as HDX engine) caninclude features of the client agent 304 discussed above in connectionwith FIG. 2 for instance, to support display a remoting protocol (e.g.,HDX or ICA). In some embodiments, the remote session agent 416 canestablish a remote desktop session and/or remote application session inaccordance to any variety of protocols, such as the Remote DesktopProtocol (RDP), Appliance Link Protocol (ALP), Remote Frame Buffer (RFB)Protocol, and ICA Protocol. For example, the remote session agent 416can establish a remote application session for a user of the clientdevice to access an enterprise network application. The remote sessionagent 416 can establish the remote application session within or over asecure connection (e.g., a VPN) established by the networking agent 412for instance.

The client application or CEB can include or be associated with a securecontainer 418. A secure container can include a logical or virtualdelineation of one or more types of resources accessible within theclient device and/or accessible by the client device. For example, thesecure container 418 can refer to the entirety of the secured portion ofthe digital workspace, or particular aspect(s) of the secured portion.In some embodiments, the secure container 418 corresponds to a securecache (e.g., electronic or virtual clipboard), and can dynamicallyincorporate a portion of a local cache of each client device of a user,and/or a cloud-based cache of the user, that is protected or secured(e.g., encrypted). The secure container can define a portion of filesystem(s), and/or delineate resources allocated to a CEB and/or tonetwork applications accessed via the CEB. The secure container caninclude elements of the secure data container 228 discussed above inconnection with FIG. 2 for example. The CEB can be configured (e.g., viapolicies) to limit, disallow or disable certain actions or activities onresources and/or data identified to be within a secure container. Asecured container can be defined to specify that the resources and/ordata within the secure container are to be monitored for misuse, abuseand/or exfiltration.

In certain embodiments, a secure container relates to or involves theuse of a secure browser (e.g., embedded browser 410 or secure browser420) that implements various enterprise security features. Networkapplications (or web pages accessed by the secure browser) that areconfigured to run within the secure browser can effectively inherit thesecurity mechanisms implemented by the secure browser. These networkapplications can be considered to be contained within the securecontainer. The use of such a secure browser can enable an enterprise toimplement a content filtering policy in which, for example, employeesare blocked from accessing certain web sites from their client devices.The secure browser can be used, for example, to enable client deviceusers to access a corporate intranet without the need for a VPN.

In some embodiments, a secure container can support various types ofremedial actions for protecting enterprise resources. One such remedy isto lock the client device, or a secure container on the client devicethat stores data to be protected, such that the client device or securecontainer can only be unlocked with a valid code provided by anadministrator for instance. In some embodiments, these and other typesof remedies can be invoked automatically based on conditions detected onthe client device (via the application of policies for instance), or canbe remotely initiated by an administrator.

In some embodiments, a secure container can include a secure documentcontainer for documents. A document can comprise any computer-readablefile including text, audio, video, and/or other types of information ormedia. A document can comprise any single one or combination of thesemedia types. As explained herein, the secure container can help preventthe spread of enterprise information to different applications andcomponents of the client device, as well as to other devices. Theenterprise system (which can be partially or entirely within a cloudnetwork) can transmit documents to various devices, which can be storedwithin the secure container. The secure container can preventunauthorized applications and other components of the client device fromaccessing information within the secure container. For enterprises thatallow users to use their own client devices for accessing, storing, andusing enterprise data, providing secure container on the client deviceshelps to secure the enterprise data. For instance, providing securecontainers on the client devices can centralize enterprise data in onelocation on each client device, and can facilitate selective or completedeletion of enterprise data from each client device when desired.

The secure container can include an application that implements a filesystem that stores documents and/or other types of files. The filesystem can comprise a portion of a computer-readable memory of theclient device. The file system can be logically separated from otherportions of the computer-readable memory of the client device. In thisway, enterprise data can be stored in a secure container and privatedata can be stored in a separate portion of the computer-readable memoryof the client device for instance. The secure container can allow theCEB, network applications accessed via the CEB, locally installedapplications and/or other components of the client device to read from,write to, and/or delete information from the file system (if authorizedto do so). Deleting data from the secure container can include deletingactual data stored in the secure container, deleting pointers to datastored in the secure container, deleting encryption keys used to decryptdata stored in the secure container, and the like. The secure containercan be installed by, e.g., the client application, an administrator, orthe client device manufacturer. The secure container can enable some orall of the enterprise data stored in the file system to be deletedwithout modifying private data stored on the client device outside ofthe secure container. The file system can facilitate selective orcomplete deletion of data from the file system. For example, anauthorized component of the enterprise's system can delete data from thefile system based on, e.g., encoded rules. In some embodiments, theclient application can delete the data from the file system, in responseto receiving a deletion command from the enterprise's system.

The secure container can include an access manager that governs accessto the file system by applications and other components of the clientdevice. Access to the file system can be governed based on documentaccess policies (e.g., encoded rules) maintained by the clientapplication, in the documents and/or in the file system. A documentaccess policy can limit access to the file system based on (1) whichapplication or other component of the client device is requestingaccess, (2) which documents are being requested, (3) time or date, (4)geographical position of the client device, (5) whether the requestingapplication or other component provides a correct certificate orcredentials, (6) whether the user of the client device provides correctcredentials, (7) other conditions, or any combination thereof. A user'scredentials can comprise, for example, a password, one or more answersto security questions (e.g., What is the mascot of your high school?),biometric information (e.g., fingerprint scan, eye-scan), and the like.Hence, by using the access manager, the secure container can beconfigured to be accessed only by applications that are authorized toaccess the secure container. As one example, the access manager canenable enterprise applications installed on the client device to accessdata stored in the secure container and to prevent non-enterpriseapplications from accessing the data stored in the secure container.

Temporal and geographic restrictions on document access may be useful.For example, an administrator may deploy a document access policy thatrestricts the availability of the documents (stored within the securecontainer) to a specified time window and/or a geographic zone (e.g., asdetermined by a GPS chip) within which the client device=must reside inorder to access the documents. Further, the document access policy caninstruct the secure container or client application to delete thedocuments from the secure container or otherwise make them unavailablewhen the specified time period expires or if the client device is takenoutside of the defined geographic zone.

Some documents can have access policies that forbid the document frombeing saved within the secure container. In such embodiments, thedocument can be available for viewing on the client device only when theuser is logged in or authenticated via the cloud services for example.

The access manager can also be configured to enforce certain modes ofconnectivity between remote devices (e.g., an enterprise resource orother enterprise server) and the secure container. For example, theaccess manager can require that documents received by the securecontainer from a remote device and/or sent from the secure container tothe remote device be transmitted through secured tunnels/connections,for example. The access manager can require that all documentstransmitted to and from the secure container be encrypted. The clientapplication or access manager can be configured to encrypt documentssent from the secure container and decrypt documents sent to the securecontainer. Documents in the secure container can also be stored in anencrypted form.

The secure container can be configured to prevent documents or dataincluded within documents or the secure container from being used byunauthorized applications or components of the client device or otherdevices. For instance, a client device application having authorizationto access documents from the secure container can be programmed toprevent a user from copying a document's data and pasting it intoanother file or application interface, or locally saving the document ordocument data as a new file outside of the secure container. Similarly,the secure container can include a document viewer and/or editor that donot permit such copy/paste and local save operations. Moreover, theaccess manager can be configured to prevent such copy/paste and localsave operations. Further, the secure container and applicationsprogrammed and authorized to access documents from the secure containercan be configured to prevent users from attaching such documents toemails or other forms of communication.

One or more applications (e.g., applications installed on the clientdevice, and/or network applications accessed via the CEB) can beprogrammed or controlled (e.g., via policy-based enforcement) to writeenterprise-related data only into the secure container. For instance, anapplication's source code can be provided with the resource name of thesecure container. Similarly, a remote application (e.g., executing on adevice other than the client device) can be configured to send data ordocuments only to the secure container (as opposed to other componentsor memory locations of the client device). Storing data to the securecontainer can occur automatically, for example, under control of theapplication, the client application, and/or the secure browser. Theclient application can be programmed to encrypt or decrypt documentsstored or to be stored within the secure container. In certainembodiments, the secure container can only be used by applications (onthe client device or a remote device) that are programmed to identifyand use the secure container, and which have authorization to do so.

The network applications 406 can include sanctioned network applications426 and non-sanctioned network applications 428. By way of anon-limiting example, sanctioned network applications 426 can includenetwork applications from Workday, Salesforce, Office 365, SAP, and soon, while non-sanctioned network applications 426 can include networkapplications from Dropbox, Gmail, and so on. For instance, FIG. 4illustrates a case where sanctioned applications 426 are accessed via aCEB. In operation (1), a user instance of a client application 404, thatis installed on client device 402, can register or authenticate with theaccess gateway 422 of cloud services 408. For example, the user canauthenticate the user to the client device and login to the clientdevice 402. The client application can automatically execute, or beactivated by the user. In some embodiments, the user can sign in to theclient application (e.g., by authenticating the user to the clientapplication). In response to the login or sign-in, the clientapplication can register or authenticate the user and/or the clientapplication with the access gateway 422.

In operation (2), in response to the registration or authentication, theaccess gateway 422 can identify or retrieve a list of enumerated networkapplications available or pre-assigned to the user, and can provide thelist to the client application. For example, in response to theregistration or authentication, the access gateway can identify the userand/or retrieve a user profile of the user. According to the identityand/or user profile, the access gateway can determine the list (e.g.,retrieve a stored list of network applications matched with the userprofile and/or the identity of the user). The list can correspond to alist of network applications sanctioned for the user. The access gatewaycan send the list to the client application or embedded browser, whichcan be presented via the client application or embedded browser to theuser (e.g., in a storefront user interface) for selection.

In operation (3), the user can initiate connection to a sanctionednetwork application (e.g., a SaaS application), by selecting from thelist of network applications presented to the user. For example, theuser can click on an icon or other representation of the sanctionednetwork application, displayed via the client application or embeddedbrowser. This user action can trigger the CEB to transmit a connectionor access request to a server that provisions the network application.The request can include a request to the server (e.g., SaaS provider) tocommunicate with the access gateway to authenticate the user. The servercan send a request to the access gateway to authenticate the user forexample.

In operation (4), the access gateway can perform SSO with the server, toauthenticate the user. For example, in response to the server's requestto authenticate the user, the access gateway can provide credentials ofthe user to the server(s) 430 for SSO, to access the selected networkapplication and/or other sanctioned network applications. In operation(5), the user can log into the selected network application, based onthe SSO (e.g., using the credentials). The client application (e.g., thenetworking agent 412 and/or the remote session agent 416) can establisha secure connection and session with the server(s) 430 to access theselected network application. The CEB can decrypt application trafficreceived via the secure connection. The CEB can monitor traffic sent viathe CEB and the secured connection to the servers 430.

In operation (6), the client application can provide information to theanalytics services 424 of cloud services 408, for analytics processing.For example, the cloud services agent 414 of the client application 404can monitor for or capture user interaction events with the selectednetwork application. The cloud services agent 414 can convey the userinteraction events to the analytics services 424, to be processed toproduce analytics.

FIG. 5 depicts an example embodiment of a system for using a securebrowser. In brief overview, the system includes cloud services 408,network applications 406 and client device 402. In some embodiments,various elements of the system are similar to that described above forFIG. 4, but that the client application (with embedded browser) is notavailable in the client device 402. A standard or typical browser may beavailable on the client device, from which a user can initiate a requestto access a sanctioned network application for instance. A networkapplication can be specified as being sanctioned or unsanctioned viapolicies that can be set by an administrator or automatically (e.g., viaartificial intelligence).

For example, in operation (1), the user may log into the networkapplication using the standard browser. For accessing a sanctionednetwork application, the user may access a predefined URL and/orcorresponding webpage of a server that provisions the networkapplication, via the standard browser, to initiate a request to accessthe network application. In some embodiments, the request can beforwarded to or intercepted by a designated gateway service (e.g., in adata path of the request). For example, the gateway service can resideon the client device (e.g., as an executable program), or can reside ona network device 432 of the cloud services 408 for instance. In someembodiments, the access gateway can correspond to or include the gatewayservice. The gateway service can determine if the requested networkapplication is a sanctioned network application. The gateway service candetermine if a CEB initiated the request. The gateway service can detector otherwise determine that the request is initiated from a source(e.g., initiated by the standard browser) in the client device otherthan a CEB. In some embodiments, there is no requirement for adesignated gateway service to detect or determine if the request isinitiated from a CEB, for example if the requested network applicationis sanctioned, that user is initiating the request via a standardbrowser, and/or that the predefined URL and/or corresponding webpage isaccessed.

In operation (2), the server may authenticate the user via the accessgateway of the cloud services 408. The server may communicate with theaccess gateway to authenticate the user, in response to the request. Forinstance, the request can include an indication to the server tocommunicate with the access gateway to authenticate the user. In someembodiments, the server is pre-configured to communicate with the accessgateway to authenticate the user, for requests to access a sanctionednetwork application. The server may send a request to the access gatewayto authenticate the user. In response to the server's request toauthenticate the user, the access gateway can provide credentials of theuser to the server 430.

In operation (3), the gateway service and/or the server can direct (orredirect) all traffic to a secure browser 420 which provides a securebrowsing service. This may be in response to at least one of: adetermination that the requested network application is a sanctionednetwork application, a determination that the request is initiated froma source other than a CEB, a determination that the requested networkapplication is sanctioned, a determination that user is initiating therequest via a standard browser, and/or a determination that thepredefined URL and/or corresponding webpage is accessed.

The user's URL session can be redirected to the secure browser. Forexample, the server, gateway service and/or the access gateway cangenerate and/or send a URL redirect message to the standard browser,responsive to the determination. The secure browser plug-in of thestandard browser can receive the URL redirect message, and can forexample send a request to access the non-sanctioned network application,to the secure browser 420. The secure browser 420 can direct the requestto the server of the non-sanctioned network application. The URLredirect message can instruct the standard browser (and/or the securebrowser plug-in) to direct traffic (e.g., destined for the networkapplication) from the standard browser to the secure browser 420 hostedon a network device. This can provide clientless access and control viadynamic routing though a secure browser service. In some embodiments, aredirection of all traffic to the secure browser 420 is initiated orconfigured, prior to performing authentication of the user (e.g., usingSSO) with the server.

In some embodiments, the gateway service can direct or request theserver of the requested network application to communicate with thesecure browser 420. For example, the gateway service can direct theserver and/or the secure browser to establish a secured connectionbetween the server and the secure browser, for establishing anapplication session for the network application.

In some embodiments, the secured browser 420 comprises a browser that ishosted on a network device 432 of the cloud services 408. The securedbrowser 420 can include one or more features of the secured browser 420described above in connection with at least FIG. 4 for instance. Thehosted browser can include an embedded browser of a CEB that is hostedon the network device 432 instead of on the client device. The hostedbrowser can include an embedded browser of a hosted virtualized versionof the CEB that is hosted on the network device 432. Similar to the CEBinstalled on the client device, traffic is routed through the CEB hostedon the network device, which allows an administrator to have visibilityof the traffic through the CEB and to remain in control for securitypolicy control, analytics, and/or management of performance.

FIG. 6 illustrates an example implementation for browser redirectionusing a secure browser plug-in. In brief overview, the implementationincludes a web browser 512 with a secure browser plug-in 516 operatingon a client device, and a hosted web browser (or secure browser) 522residing on a network device. The web browser 512 can correspond to astandard browser, instead of an embedded browser as discussed above inconnection with FIG. 4 for example. The secure browser plug-in 516 canexecute within a first network 510 and access a server 532 in a secondnetwork 530. The first network 510 and the second network 530 are forillustration purposes and may be replaced with fewer or additionalcomputer networks. A secure browser plug-in 516 can be installed on thestandard browser 512. The plug-in can include one or more components.One such component can include an ActiveX control or Java control or anyother type and/or form of executable instructions capable of loadinginto and executing in the standard browser. For example, the standardbrowser can load and run an Active X control of the secure browserplug-in 516, in a memory space or context of the standard browser. Insome embodiments, the secure browser plug-in can be installed as anextension on the standard browser, and a user can choose to enable ordisable the plugin or extension. The secure browser plug-in cancommunicate and/or operate with the secured browser 420 for securing,using and/or accessing resources within the secured portion of thedigital workspace.

By using the secure browser plug-in 516 operating within the standardbrowser 512 network applications accessed via the standard browser 512can be redirected to a hosted secure browser. For instance, the securebrowser plug-in 516 can be implemented and/or designed to detect that anetwork application is being accessed via the standard browser, and candirect/redirect traffic from the client device associated with thenetwork application, to the hosted secure browser. The hosted securebrowser can direct traffic received from the network application, to thesecure browser plug-in 516 and/or a client agent 514 for renderingand/or display for example. The client agent 514 can execute within theweb browser 512 and/or the secure browser plug-in, and can includecertain elements or features of the client application 404 discussedabove in connection with at least FIG. 4 for example. For instance, theclient agent 514 can include a remote session agent 418 for renderingthe network application at the web browser 512. In some embodiments, thenetwork application is rendered at the hosted secure browser, and therendered data is conveyed or mirrored to the secure browser plug-in 516and/or the client agent 514 for processing and/or display.

By way of an example, a user may be working remotely and may want toaccess a network application that is internal to a secure corporatenetwork while the user is working on a computing device connected to anunsecure network. In this case, the user may be utilizing the standardbrowser 512 executing in the first network 510, in which the firstnetwork 510 may comprise an unsecure network. The server 430 that theuser wants to access may be on the second network 530, in which thesecond network 530 comprises a secure corporate network for instance.The user might not be able to access the server 430 from the unsecurefirst network 510 by clicking on an internal uniform record locator(URL) for the secure website 532. That is, the user may need to utilizea different URL (e.g., an external URL) while executing the standardbrowser 512 from the external unsecure network 510. The external URL maybe directed to or may address one or more hosted web browsers 522configured to access server(s) 430 within the second network 530 (e.g.,secure network). To maintain secure access, the secure browser plug-in516 may redirect an internal URL to an external URL for a hosted securebrowser.

The secure browser plug-in 516 may be able to implement networkdetection in order to identify whether or not to redirect internal URLsto external URLs. The standard browser 512 may receive a requestcomprising an internal URL for a website executing within the securenetwork. For example, the standard browser 512 may receive the requestin response to a user entering a web address (e.g., for secure website532) in the standard browser. The secure browser plug-in 516 mayredirect the user web browser application 512 from the internal URL toan external URL for a hosted web browser application. For example, thesecure browser plug-in 516 may replace the internal URL with an externalURL for the hosted web browser application 522 executing within thesecure network 530.

The secure browser plug-in 516 may allow the client agent 514 to beconnected to the hosted web browser application 522. The client agent514 may comprise a plug-in component, such as an ActiveX control or Javacontrol or any other type and/or form of executable instructions capableof loading into and executing in the standard browser 512. For example,the client agent 514 may comprise an ActiveX control loaded and run by astandard browser 512, such as in the memory space or context of the userweb browser application 512. The client agent 514 may be pre-configuredto present the content of the hosted web browser application 522 withinthe user web browser application 512.

The client agent 514 may connect to a server or the cloud/hosted webbrowser service 520 using a thin-client or remote-display protocol topresent display output generated by the hosted web browser application522 executing on the service 520. The thin-client or remote-displayprotocol can be any one of the following non-exhaustive list ofprotocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

The hosted web browser application 522 may navigate to the requestednetwork application in full-screen mode, and can render the requestednetwork application. The client agent 514 may present the content orrendition of the network application on the web browser application 512in a seamless and transparent manner such that it appears that thecontent is being displayed by the standard browser 512, e.g., based onthe content being displayed in full screen mode. In other words, theuser may be given the impression that the web site content is displayedby the user web browser application 512 and not by the hosted webbrowser application 522. The client agent 514 may transmit navigationcommands generated by the user web browser application 512 to the hostedweb browser application 522 using the thin-client or remote-displayprotocol. Changes to the display output of the hosted web browserapplication 522, due to the navigation commands, may be reflected in theuser web browser application 512 by the client agent 514, giving theimpression to the user that the navigation commands were executed by theuser web browser application 512.

Referring again to FIG. 5, and in operation (4), a new browser tab canopen on the standard browser, to render or display the secure browsersession. The new browser tab can be established or opened by the securebrowser plug-in for instance. The secure browser plug-in and/or a clientagent can receive data from the secure browser session, and can renderthe network application within the new browser tab as discussed above inconnection with FIG. 6 for instance.

In operation (5), the secure browser can feed all user interactionevents via the network application, back to analytics service forprocessing. The secure browser plug-in can monitor for and intercept anyuser interaction events directed to the rendition of the networkapplication within the browser tab. Hence, a user can use a native (orstandard) browser to access a network application while allowingvisibility into the network application's traffic, via theinteroperation of cloud services and a secure browser (in the absence ofthe client application).

FIG. 7 depicts another example embodiment of a system of using a securebrowser. In brief overview, the system includes cloud services 408,network applications 406 and the client device 402. In some embodiments,various elements of the system are similar to that described above forFIG. 5. A client application with embedded browser is not available inthe client device 402. A standard or typical (e.g., HTML5) browser isavailable on the client device, from which a user can initiate a requestto access a non-sanctioned network application. A network applicationcan be specified as being sanctioned or non-sanctioned via policies thatcan be set by an administrator or automatically (e.g., via artificialintelligence).

In operation (1), the user may attempt to log into a non-sanctionednetwork application using the standard browser. The user may attempt toaccess a webpage of a server that provisions the network application,and to initiate a request to access the network application. In someembodiments, the request can be forwarded to or intercepted by adesignated gateway service (e.g., in a data path of the request). Forexample, the gateway service (sometimes referred to as SWG) can resideon the client device (e.g., as an executable program), or can reside ona network device 432 of the cloud services 408 for instance. The gatewayservice can detect or otherwise determine if the requested networkapplication is a sanctioned network application. The gateway service candetermine if a CEB initiated the request. The gateway service can detector otherwise determine that the request is initiated from a source(e.g., initiated by the standard browser) in the client device otherthan a CEB.

In operation (2), the gateway service detects that the requested networkapplication is a non-sanctioned network application. The gateway servicecan for instance extract information from the request (e.g., destinationaddress, name of the requested network application), and compare theinformation against that from a database of sanctioned and/ornon-sanctioned network applications. The gateway service can determine,based on the comparison, that the requested network application is anon-sanctioned network application.

In operation (3), responsive to the determination, the gateway servicecan block access to the requested network application, e.g., by blockingthe request. The gateway service can generate and/or send a URL redirectmessage to the standard browser, responsive to the determination. TheURL redirect message can be similar to a URL redirect message sent fromthe server to the standard browser in FIG. 5 in operation (3). A securebrowser plug-in of the standard browser can receive the URL redirectmessage, and can for example send a request to access the non-sanctionednetwork application, to the secure browser 420. The secure browser 420can direct the request to the server of the non-sanctioned networkapplication.

The server of the non-sanctioned network application may authenticatethe user via the access gateway of the cloud services 408, e.g.,responsive to receiving the request from the secure browser. The servermay communicate with the access gateway to authenticate the user, inresponse to the request. The server may send a request to the accessgateway to authenticate the user. In response to the server's request toauthenticate the user, the access gateway can provide credentials of theuser to the server 430. Upon authentication, the secure browser (or acorresponding CEB) can establish a secured connection and an applicationsession with the server.

In operation (4), a new browser tab can open on the standard browser, torender or display the secure browser's application session. The newbrowser tab can be established or opened by the secure browser plug-infor instance. The secure browser plug-in and/or a client agent canreceive data from the secure browser session, and can render the networkapplication within the new browser tab as discussed above in connectionwith FIGS. 5-6 for instance.

In operation (5), the secure browser can feed all user interactionevents via the network application, back to analytics service forprocessing. The secure browser plug-in can monitor for and intercept anyuser interaction events directed to the rendition of the networkapplication within the browser tab. Hence, a user can use a native (orstandard) browser to access a network application while allowingvisibility into the network application's traffic, via theinteroperation of cloud services and a secure browser (in the absence ofthe client application).

In some embodiments, in the absence or non-availability of a CEB on theclient device, browser redirection is performed so that each requestednetwork application is accessed via a corresponding hosted securebrowser (or hosted CEB) for handling, instead of having all trafficredirected through a single hosted secure browser (or hosted CEB). Eachdedicated secure browsers can provide compartmentalization and improvedsecurity.

The use of a CEB, whether hosted or local to the client device, canallow for end-to-end visibility of application traffic for analytics,service level agreement (SLA), resource utilization, audit, and so on.In addition to such visibility, the CEB can be configured with policiesfor managing and controlling any of these as well as other aspects. Forexample, DLP features can be supported, to control “copy and paste”activities, download of files, sharing of files, and to implementwatermarking for instance. As another example, the CEB can be configuredwith policies for managing and controlling access to local drives and/ordevice resources such as peripherals.

Referring now to FIG. 8, an example embodiment of a system for usinglocal embedded browser(s) and hosted secured browser(s) is depicted. Anenvironment is shown where different types of client devices 402A, 402Bmay be used (e.g., in a BYOD context), such that one may be locallyequipped with a suitable CEB, and another client device may not have asuitable local CEB installed. In such an environment, systems describedin FIGS. 4, 5 and 7 can be used to support each client devices based onthe availability of a locally installed and suitable CEB.

FIG. 9 depicts an example process flow for using local embeddedbrowser(s) and hosted secured browser(s). The process flow can be usedin the environment described above in FIG. 8, to determine whether anembedded browser or a hosted secured browser should be used for eachclient device to access a network application. For example, in operation901, a HTTP client can attempt to access a web service (e.g., server ofa network application). In operation 903, the web service can redirectthe HTTP client to a gateway service for authentication. In operation906, the gateway service can determine if the HTTP client is a CEB. Ifso, in operation 909, the gateway service can determine if the CEB is asuitable CEB, e.g., capable of enforcing defined application policies.If so, in operation 911, the CEB is allowed access to the web service,and can enforce the defined policies.

If the gateway service determines that the HTTP client is not a CEB, thegateway service can cause a virtualized version of a CEB to beinitialized and hosted on a remote server (e.g., a network device 432 ofcloud services 408), in operation 907. In some embodiments, such ahosted CEB may already be available on a network device 432, and can beselected for use. For example in operation 911, the CEB is allowedaccess to the web service, and can enforce the defined policies.

If the gateway service determines that the HTTP client is a CEB, butthat the CEB is not a suitable CEB, the gateway service can cause avirtualized version of a CEB to be initialized and hosted on a remoteserver (e.g., a network device 432 of cloud services 408), in operation907. In some embodiments, such a hosted CEB may already be available ona network device 432, and can be selected for use. For example inoperation 911, the CEB is allowed access to the web service, and canenforce the defined policies.

In some embodiments, if the user is requesting access to a webapplication located in a company data center, the gateway service (incloud service or on premise) can allow access when the clientapplication with CEB is detected. Otherwise, the request can be routedto a service with the hosted virtualized version of the CEB, and thenaccess is authenticated and granted.

At operation 905 and/or operation 909 for instance, the decisions madeon whether the HTTP client is a CEB and whether it is a suitable CEB maybe determined by a number of factors. For example, to determine if theHTTP client is CEB, the gateway service may take into account factors,for example including at least one of: user Identity and strength ofauthentication, client Location, client IP Address, how trusted the useridentity, client location, client IP are, jailbreak status of the clientdevice, status of anti-malware software, compliance to corporate policyof the client device, and/or remote attestation or other evidence ofintegrity of the client software.

To determine if the CEB is able to honor or support all definedapplication policies (which may vary by client version, client OSplatform and other factors), the client device's software and gatewayservice may perform capability negotiation and/or exchange versioninformation. In some embodiments, the gateway service can query or checka version number or identifier of the CEB to determine if the CEB is asuitable CEB to use.

Driving all the traffic though the CEB then allows additional control ofcontent accessing SaaS and Web based systems. Data Loss Prevention (DLP)of SaaS and Web traffic can be applied through the CEB app with featuresincluding copy and paste control to other CEB access applications or ITmanaged devices. DLP can also be enforced by enabling content to bedownloaded only to designated file servers or services under IT control.

Referring now to FIG. 10, depicted is an example embodiment of a systemfor managing user access to webpages. Some webpages (or websites) areknown to be safe while others may be suspect. A user may access awebpage via a corresponding URL through a standard browser. For example,the user may click on a link corresponding to the URL, which may beincluded in an email being viewed using a mail application. An accessgateway (SWG) may intercept an access request generated by the clickingof the link, and can determine if the corresponding URL is safe orsuspect. If the URL is known to be safe, the access gateway can allowthe request to proceed to the corresponding website or web server. Ifthe URL is suspect, the access gateway can redirect the request to behandled via a hosted secure browser. The secure browser can requestaccess for, and access the webpage (on behalf of the standard browser),and can allow the webpage information to be conveyed to the standardbrowser, similar to the handling of a network application via browserredirection as discussed in connection with at least FIGS. 7 and 5.

C. Systems and Methods for Traffic Inspection Via Embedded Browsers

When moving from a locally hosted setup to a remote server (e.g., aspart of Software as a Service (SaaS), Infrastructure as a Service(IaaS), and Platform as a Service (PaaS)), users may lose a degree ofcontrol over quality of service, management, and data flow to the remoteserver. As part of the move, there may be a prearranged set of operationconditions regarding performance (e.g., service level agreement). As aclient accesses resources of an application hosted on the remote server,the remote server may gather performance data. The server may alsogather analytical data from the aggregated performance data usingvarious tools. The client, on the other hand, may not have access to theperformance data. As such, the user of the client may have difficultyverifying that the remote service is providing the resources inaccordance with the prearranged set of operation conditions.

With cloud-based services, the applications may be delivered over aTransport Layer Security (TLS) or a Secure Sockets Layer (SSL)connection. Consequently, under existing techniques, networking-relatedmonitoring of the data flow from the client to the cloud-based servicemay lack the types of information available when the application waslocally installed. This may become problematic as application behaviormay vary from endpoint to endpoint. In addition, since currentencryption techniques may be unable to peer into the data flow betweenthe client and the cloud-based service, the network-related monitoringmay not be sufficient enough to detect and prevent information leakage.

To alleviate the technical drawbacks arising from moving an applicationfrom a self-hosted setup to a remote server, an embedded browser canintercept all communications for the application between the client andthe server. By intercepting the communications, the embedded browser maygather application telemetry data, such as HTTP message exchanges(including addresses, time, size, and status codes, etc.), processorusage, memory consumption, disk usage, and JavaScript engine statistics,among others. In addition, the application telemetry data may beaggregated on the client-side to create behavior profiles for anomalydetection. Furthermore, customer monitoring alerting mechanisms can beintegrated with the server-side analytics monitoring systems to create afeedback loop for the client-side application telemetry data monitoring.As the embedded browser is able to intercept all communications from theclient to the remote server, the embedded browser may use variouspattern recognition techniques to identify sensitive information and mayprevent the leakage of such information to the remote server.

Referring to FIG. 11, depicted is a block diagram of a system 1100 forinspecting traffic communicated with network applications (e.g., SaaS orWeb applications) that are accessed via a client application 404 withembedded browser 410 (CEB). The system 1100 may include a clientapplication 404 (as described herein above) and network applications1105. The network applications 1105 may include one or more applications1110A-N (hereinafter generally referred to as application 1110) and atelemetry tracker engine 1120. Each application 1110A-N may include asanctioned application 426 or a non-sanctioned application 428 of thenetwork applications 406 as previously detailed herein. The clientapplication 404 may include an embedded browser 410 (as detailed hereinabove) and an application inspector module 1115. The applicationinspector module 1115 may include an analytics tracking engine 1135, abehavior modeler engine 1140, and a data controller engine 1145. In someembodiments, the application inspector module 1115 may be a part of theembedded browser 410 (e.g., as a plug-in). In some embodiments, theapplication inspector module 1115 may be a part of the clientapplication 404 but separate from the embedded browser 410. In someembodiments, the application inspector module 1115 may be separate fromthe client application 404 and executing on the same client executingthe client application 404. In some embodiments, the applicationinspector module 1115 may reside on another device separate from theclient executing the client application 404 (e.g., reside on anintermediary device between the client and one or more servers hostingthe applications 1110).

Each of the above-mentioned elements or entities is implemented inhardware, or a combination of hardware and software, in one or moreembodiments. Each component of the system 1100 may be implemented usinghardware or a combination of hardware or software detailed above inconnection with FIG. 1. For instance, each of these elements or entitiescan include any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of a client device (e.g., the client application 404) or one ormore servers (e.g., network applications 1105). The hardware includescircuitry such as one or more processors in one or more embodiments.

A client device executing the client application 404 may be incommunication with one or more servers hosting the network applications1105 via a secure communication channel 1130. In some embodiments,secure communication channel 1130 may be established between the clientand the one or more servers in accordance with the Transport LayerSecurity (TLS), Secure Socket Tunneling Protocol (SSTP), and InternetProtocol Security (IPsec) communication protocols, among others. Networktraffic travelling through the secure communications channel 1130 may beencrypted using a cryptographic key. The secure communications channel1130 may be established as part of a communication session between theembedded browser 410 (or CEB) and the application 1110. In establishingthe communication session, the cryptographic key (e.g., a public key)may be distributed to the client running the client application 404 andthe one or more servers running the application 1110, wherein theapplication 1110 is accessed via the embedded browser 410.

The embedded browser 410 may provide access to one of the applications1110A-N via the secure communication channel 1130. For example, usingthe embedded browser 410, a user of the client may interact with andinvoke various functionalities of the application 1110 through agraphical user interface of the application 1110 displayed via theembedded browser 410. In accessing the application 1110, the clientexecuting the embedded browser 410 and the one or more servers hostingthe application 1110 may exchange network traffic via the securecommunications channel 1130. The network traffic may include one or morepackets exchanged in accordance with the communications protocol for thesecure communications channel 1130 established between the client andthe one or more servers. Each packet may be generated in accordance withthe Hypertext Transfer Protocol (HTTP). The HTTP message may include aheader and a body. In some embodiments, the HTTP message may include arequest message from the embedded browser 410 to the application 1110.In some embodiments, the HTTP message may be a response message from theapplication 1110 to the embedded browser 410. The header of the HTTPmessage may include one or more fields, such as a function, a statuscode, a time-stamp, a content type, a content encoding, and a host,among other information. The body of the HTTP message may include amessage. In some embodiments, the message may include data of theapplication 1110 to be rendered by the embedded browser 410. In someembodiments, the message may include data from the client devicedestined for a server of the application 1110 via the embedded browser410. With the embedded browser 410 having visibility into the HTTPmessages exchanged between the client and the servers of theapplications 1110, information about the HTTP messages and traffic canbe used to form analytics data. This provides another avenue forgenerating analytics from the client side, in addition to analyticsgenerated on the server side.

On the server side, the telemetry tracker engine 1120 may receive orgather information about the network traffic exchanged via the securecommunications channel 1130 between the client running the clientapplication 404 and the one or more servers running the application1110. In some embodiments, the telemetry tracker engine 1120 mayidentify the one or more packets communicated via the securecommunications channel 1130. Once identified, the telemetry trackerengine 1120 may decrypt the one or more packets using the cryptographickey used to establish the secure communications channel 1130. The one ormore packets may include HTTP messages to be sent to the embeddedbrowser 410 and HTTP messages received from the embedded browser 410.For each packet communicated via the secure communications channel 1130,the telemetry tracker engine 1120 may parse the packet to identify theheader and the body. The telemetry tracker engine 1120 may parse theheader to identify content of the header (e.g., one or more fields). Thetelemetry tracker engine 1120 may parse the body of the HTTP message toidentify contents of the body (e.g., data to be rendered by the embeddedbrowser 410 or to be used by the application 1110).

Based on the packets exchanged as part of the network traffic via thesecure communications channel 1130, the telemetry tracker engine 1120may generate analytics data. In some embodiments, the telemetry trackerengine 1120 can receive application telemetry from the client-side, togenerate analytics data. The analytics data generated by the telemetrytracker engine 1120 may include one or more computing resourceperformance metrics and one or more network performance metrics. Thecomputing resource performance metrics may include a processor usage(sometimes referred to as CPU usage), a response time, a processing time(sometimes referred to as CPU time), memory consumption, and hard diskconsumption, among others of the client running the embedded browser410. The network traffic performance metrics may include networkbandwidth consumption, a network throughput, network latency, sessionduration, an engagement time, an interaction rate, and a packet exchangerate, among others of the client running the embedded browser 410. Insome embodiments, the analytics data may include metadata for the clientrunning the client application 404, the embedded browser 410 of theclient application 404, the secure communications channel 1130, and theapplication 1110, among others. The metadata may include a location ofthe client, an account identifier of a user operating the embeddedbrowser 410, a version number of the client application 404, a versionnumber of the embedded browser 410, and/or a network type of the securecommunication channel 1130, among others.

To generate the analytics data, the telemetry tracker engine 1120 mayuse information about application traffic parsed on the server side.Client-side telemetry, comprising certain information about the clientand/or about the application traffic received via the communicationschannel 1130 on the client side, may be used to form analytics data. Insome embodiments, the telemetry tracker engine 1120 may send a requestto the client for the client-side telemetry. The request for client-sidetelemetry may be sent periodically. Subsequently, the client may sendthe client-side telemetry (e.g., via one or more HTTP messages) via thesecure communications channel 1130. In some embodiments, the client-sidetelemetry may include the computing resource performance metrics, suchas the processor usage, the processing time, memory consumption, andhard disk consumption, among others. In some embodiments, theclient-side telemetry may include network traffic performance metrics,such as the network bandwidth consumption, the network throughput, thesession duration, network latency, the engagement time, the interactionrate, and/or the packet exchange rate, among others. In someembodiments, the client-side telemetry may include metadata. Byreceiving and using the client-side telemetry, the telemetry trackerengine 1120 may generate the analytics data.

In some embodiments, the telemetry tracker engine 1120 may generate theanalytics data, without using the client-side telemetry. To generate thenetwork traffic performance metrics, the telemetry tracker engine 1120may monitor the network traffic of the secure communications channel1130 on the server-side. In some embodiments, the telemetry trackerengine 1120 may identify a number of packets exchanged via the securecommunications channel 1130 over a predefined time period. Based on thenumber of packets identified as exchanged over the predefined timeperiod, the telemetry tracker engine 1120 may determine a frequency ofthe packets exchanged via the secure communications channel 1130. Insome embodiments, the telemetry tracker engine 1120 may determine a sizeof each packet exchanged via the secure communications channel 1130.Using the number, size, and/or frequency of the packets transmitted viathe secure communication channel 1130, the telemetry tracker engine 1120may determine the network bandwidth consumption, the network throughput,and the packet exchange rate, among other measures.

On the client side, the analytics tracking engine 1135 may identify thenetwork traffic exchanged via the secure communications channel 1130between the client running the client application 404 and the one ormore servers running the application 1110. Similar to the telemetrytracker engine 1120, the analytics tracking engine 1135 may generateanalytics data based on application traffic visible to the embeddedbrowser 410 i. The analytics tracking engine 1135, however, maydetermine the analytics data associated with packets sent from theclient via the client application 404 to the one or more servers hostingthe application 1110. For example, the analytics tracking engine 1135may monitor one or more packets to be sent via the securedcommunications channel 1130 from the embedded browser 410. The one ormore packets may be intercepted and analyzed prior to encryption usingthe cryptographic key for the secure communication channel 1130.

The analytics data generated by the analytics tracking engine 1135 mayinclude one or more computing resource performance metrics one or morenetwork performance metrics. The computing resource performance metricsmay include a processor usage (sometimes referred to as CPU usage), aprocessing time (sometimes referred to as CPU time), a response time,memory consumption, and hard disk consumption, among others of theclient related to the use of the application 1110. The network trafficperformance metrics may include network bandwidth consumption, networklatency, a network throughput, session duration, an engagement time, aninteraction rate, and a packet exchange rate, among others. In someembodiments, the analytics data may include metadata of the clientrunning the client application 404, the embedded browser 410 of theclient application 404, the secure communications channel 1130, and/orthe application 1110, among others. The metadata may for instanceinclude a location of the client, an account identifier of a useroperating the embedded browser 410, a version number of the clientapplication 404, a version number of the embedded browser 410, and/or anetwork type of the secure communication channel 1130, among others.

To generate the computing resource performance metrics, the analyticstracking engine 1135 may monitor computing resources at the clientrunning the client application 404. As the embedded browser 410 isaccessing the application 1110, the analytics tracking engine 1135 maymonitor the computing resources at the client allocated to the embeddedbrowser 410 in providing access to the application 1110 for instance. Insome embodiments, the analytics tracking engine 1135 may monitor thecomputing resources allocated to the embedded browser 410 in carryingout the functionalities of the application 1110. The analytics trackingengine 1135 may monitor the processor usage, the processing time, theresponse time, the memory consumption, and the hard disk consumptionassociated with the use of the application 1110. In some embodiments,the analytics tracking engine 1135 may monitor network traffic of thesecure communications channel 1130 in determining the computing resourceperformance metrics. In some embodiments, the analytics tracking engine1135 may identify a time of an HTTP message from the one or more servershosting the application 1110 and a time of an HTTP message sent by theembedded browser 410 in response to the HTTP message from the one ormore servers. Using the time of the HTTP message from the one or moreservers hosting the application 1110 and the time of the HTTP messagesent by the embedded browser 410 in response, the analytics trackingengine 1135 may determine the response time as part of the computingresources performance metrics.

To generate the network traffic performance metrics, the analyticstracking engine 1135 may monitor the network traffic passing into and/orout of the secure communications channel 1130. In some embodiments, theanalytics tracking engine 1135 may intercept and/or monitor the networktraffic (including the one or more packets) prior to transmission viathe secure communications channel 1130. In some embodiments, theanalytics tracking engine 1135 may identify a number of packets to besent or received via the secure communications channel 1130 over apredefined time period. Based on the number of packets identified asexchanged over the predefined time period, the analytics tracking engine1135 may determine a frequency of the packets to be sent or received viathe secure communications channel 1130. In some embodiments, theanalytics tracking engine 1135 may determine a size of each packet to besent or received via the secure communications channel 1130. Using thenumber, size, and/or frequency of the packets exchanged via the securecommunication channel 1130, the analytics tracking engine 1135 maydetermine the network bandwidth consumption, the network throughput, thenetwork latency, and the packet exchange rate, among other measures, inthe embedded browser 410 accessing resources of the application 1110.

In some embodiments, the analytics tracking engine 1135 may generatemetadata. As discussed above, the metadata for the analytics data may bethose regarding the client running the client application 404, theembedded browser 410 of the client application 404, the securecommunications channel 1130, and the application 1110, among others. Insome embodiments, the analytics tracking engine 1135 may identify thelocation of the client (e.g., geographic coordinates, Internet Protocol(IP) address, and Media Access Control (MAC) address) running the clientapplication 404. In some embodiments, the analytics tracking engine 1135may identify the account identifier of the user logged into the embeddedbrowser 410. In some embodiments, the analytics tracking engine 1135 mayidentify the version number of the client application 404. In someembodiments, the analytics tracking engine 1135 may identify the versionnumber of the embedded browser 410. In some embodiments, the analyticstracking engine 1135 may identify network type of the securecommunication channel 1130 (e.g., Intranet or Intranet).

With the generation of the analytics data, the analytics tracking engine1135 may maintain the analytics data in a database. As the analyticsdata is continually regenerated, the analytics tracking engine 1135 mayupdate the analytics data in the database. In some embodiments, thedatabase may be local to the client running the client application 404or shared between multiple clients running the respective clientapplications 404. In some embodiments, the database may reside with thenetwork applications 1105, such as the one or more servers hosting theapplication 1110. The analytics tracking engine 1135 may provide thegenerated analytics data to the telemetry tracker engine 1120. In someembodiments, the analytics tracking engine 1135 may receive a requestfor the analytics data from the telemetry tracker engine 1120 or from anadministrator of the client application 404. In response to the receiptof the request, the analytics tracking engine 1135 may access theanalytics data maintained on the database. The analytics tracking engine1135 may generate a response message using the analytics data. The bodyof the response message may include the analytics data maintained by theanalytics tracking engine 1135. Once generated, the analytics trackingengine 1135 may send the response message to the telemetry trackerengine 1120 via the secured communication channel 1130. The analyticstracking engine 1135 may also provide the response message with theanalytics data to the administrator of the client application 404.

In this manner, the analytics tracking engine 1135 may provide a morecomplete end-to-end description of the performance metrics of theapplication 1110. Furthermore, the administrator of the clientapplication 404 may verify whether the service provider of theapplication 1110 is adhering to the prearranged set of operationconditions (sometimes referred to as a service level agreement (SLA)).The prearranged set of operation conditions may include an expectedresponse time, turn-around time, recovery time, network bandwidthavailability, among others.

Using the analytics data accumulated for the embedded browser 410, thebehavior modeler engine 1140 may maintain a user behavior model for auser of the application 1110. The user behavior model may be a machinelearning model to characterize and predict the user interactions withthe application 1110 accessed via the embedded browser 410. The userbehavior model may have a set of inputs, a set of weights, and a set ofoutputs. The set of inputs may include the analytics data. The analyticsdata may be simulated user behavior. The set of weights may relate theoutputs to the inputs. The set of outputs may include a predictedbehavior of the user and a deviation measure between an expected userbehavior to a simulated user behavior, among others. In someembodiments, the behavior modeler engine 1140 may use the analytics datagenerated by the analytics tracking engine 1135 as training data for theuser behavior model. In some embodiments, the analytics data may beaggregated from multiple clients running the embedded browser 410 inaccessing the application 1110. The aggregated analytics data frommultiple clients may be greater in size that the analytics data from asingle client. In training the user behavior model, the behavior modelerengine 1140 may modify, adjust, or set the set of weights of the userbehavior model.

Once the user behavior model is trained, the behavior modeler engine1140 may monitor or instrument the operations of the embedded browser410 in providing access to the application 1110. In some embodiments,the behavior modeler engine 1140 may aggregate the measured operationsof the application 1110. The behavior modeler engine 1140 may use theaggregated operations the input to the user behavior model. Using theaggregated operations, the behavior modeler engine 1140 may determinewhether the operations of the application 1110 indicates an anomaly oris within expected behaviors. In some embodiments, the behavior modelerengine 1140 may generate the deviation measure between the expectedbehavior and the measured behavior using the measured operations. Insome embodiments, the behavior modeler engine 1140 may compare thedeviation measure to a predefined threshold. If the deviation measure isdetermined to be greater than the predetermined threshold, the behaviormodeler engine 1140 may determine that the measured operations areanomalous. In some embodiments, the behavior modeler engine 1140 maysend a notification message to an administrator of the application 1110and/or the administrator of the client application 404. Conversely, ifthe deviation measure is determined to be less than or equal to thepredetermined threshold, the behavior modeler engine 1140 may determinethat the operations are not anomalous.

The data controller engine 1145 may control the network traffic from theclient running the client application 404 to the one or more servershosting the application 1110. In some embodiments, the data controllerengine 1145 may apply a policy to each packet from the embedded browser410 to the application 1110 to determine whether transmission of thepacket is permitted. The policy may specify a set of predefined datatypes labeled as potentially sensitive information (e.g., personallyidentifiable information (PII), health records, and financial records).In some embodiments, the policy may include a format or a regularexpression for each data type labeled as potentially sensitiveinformation. In applying the policy, the data controller engine 1145 mayintercept all packets sent via the embedded browser 410. The packet maythen be transmitted via the secure communications channel 1130, oncechecked against the policy. Based on the policy, the data controllerengine 1145 may determine whether to permit transmission of the packetto the one or more servers hosting the application 1110. If the packetto be transmitted contains information matching one of the predefineddata types, the data controller engine 1145 may restrict thetransmission of the packet to the application 1110. On the other hand,if the packet to be transmitted to the application 1110 does not containinformation matching any of the predefined data types, the datacontroller engine 1145 may permit the transmission of the packet.

In some embodiments, the data controller engine 1145 may control thetransmission of the packet based on the identity, behavior and/orprofile of the application 1110. In some embodiments, the policy mayspecify a whitelist of applications permitted to receive the packetscontaining potentially sensitive information. The policy may alsoinclude a blacklist of applications restricted from receiving thepackets containing potentially sensitive information. If the application1110 matches the whitelist of applications or does not match any one theblacklist of applications, the data controller engine 1145 may permitthe transmission of the packet to the application 1110, even when thepacket is determined to contain sensitive information. On the otherhand, if the application 1110 matches the blacklist of applications ordoes not match any one the whitelist of applications, the datacontroller engine 1145 may restrict the transmission of the packet tothe application 1110, even when the packet is determined to not tocontain any sensitive information.

In some embodiments, the data controller engine 1145 may control thetransmission of the packet based on a destination of the packet. Thedestination may include the one or more servers hosting the application1110 or another remote server. The destination may be defined by a IPaddress, a MAC address, or a Uniform Resource Locator (URL). In someembodiments, the policy may specify a whitelist of destinationspermitted to receive the packets containing potentially sensitiveinformation. The policy may also include a blacklist of destinationsrestricted from receiving the packets containing potentially sensitiveinformation. If the application 1110 matches the whitelist ofdestinations or does not match any of the blacklist of destinations, thedata controller engine 1145 may permit the transmission of the packet tothe application 1110, even when the packet is determined to containsensitive information. On the other hand, if the application 1110matches the blacklist of destinations or does not match any of thewhitelist of destinations, the data controller engine 1145 may restrictthe transmission of the packet, even when the packet is determined tonot to contain any sensitive information.

In some embodiments, the data controller engine 1145 may control thetransmission of the packet based on the user behavior model trained bythe behavior modeler engine 1140 1145. The data controller engine 1145may monitor or instrument the operations of the embedded browser 410 inproviding access to the application 1110.

Referring to FIG. 12, depicted is a process diagram for an environment1200 for gathering analytics of traffic monitored via the embeddedbrowser 410. The environment 1200 may include the components of thesystem 1100 described herein above. The environment 1200 may be dividedonto a customer side 1205 (sometimes referred to as client-side) and avendor side 1215 (sometimes referred to as server-side). The customerside 1205 may include an embedded browser 410 used by an operator 1235(sometimes referred to as an administrator). The vendor side 1215 mayinclude an application server 1210 hosting the application 1100maintained by an operator 1240 (sometimes referred to as anadministrator).

In providing client access to the application 1110 hosted on theapplication server 1210, the embedded browser 410 may exchange data 1220with the application server 1210. In doing so, the embedded browser 410may generate application telemetry data 1225 (e.g., using the analyticstracking engine 1135). The application telemetry data 1225 may includenetwork performance metrics, computing resource performance metrics, andmetadata in relation to the embedded browser 410 enabling access to theapplication 1110 hosted on the application server 1210. The applicationtelemetry data 1225 may be provided to the operator 1235 as well as theapplication server 1210 hosting the application 1110. The applicationserver 1210 in turn may use the application telemetry data from thecustomer side 1205 as well data communicated with the embedded browser410 to generate application and server-side telemetry data. Theapplication and server-side telemetry data may be provided to theoperator 1240. In this manner, operators 1235 and 1240 in theenvironment 1200 may be able to be provided with end-to-end performancedata with regards to the application 1110.

Referring to FIG. 13A, depicted is a process diagram for an environment1300 for controlling traffic from the embedded browser 410. Theenvironment 1300 may include the components of the system 1100 describedherein above. The environment 1300 may include the embedded browser 410administered by a security operator 1310, a company application server1305A, and a personal application server 1305B. The embedded browser 410may control access to, or operations associated with, a trustedapplication 1105A and an untrusted application 1105B. The applications1105A and 1105B may be set as trusted or untrusted under anadministrated policy set by the security operator 1310. In operation(1), the embedded browser 410 may access the company application 1305Avia the trusted application 1105A to retrieve a document file. Theadministrative policy may permit the trusted application 1105A to read,copy, and edit the document file, but may restrict the untrustedapplication 1105B to read, copy, or edit the document file. In operation(2), a user of the embedded browser 410 may copy the document file fromthe trusted application 1105A to the untrusted application 1105B. Inoperation (3), when the user attempts to send the document file to apersonal application server 1305B, the transfer of the document file maybe blocked in accordance with the administrative policy. Moreover, inoperation (4), the security operator 1310 may be alerted as to theattempt to transfer the document file from the company applicationserver 1305A to an authorized location.

Referring to FIG. 13B, depicted is a process diagram for an environment1330 for controlling traffic from the embedded browser 410. Theenvironment 1330 may include the components of the system 1100 describedherein above. The environment 1330 may include the embedded browser 410administered by a security operator 1310 and a company applicationserver 1305A. The embedded browser 410 may access the trustedapplication 1105A. The trusted application 1105A may be hosted on thecompany application server 1305A. The embedded browser 410 may besubject to an administrative policy set by the operator 1310 to blockany transfers of sensitive information. In operation (1), a user of theembedded browser 410 may attempt to copy a document file containingsensitive information to a company application server 1305. In operation(2), the security operator 1310 may be alerted as to the attempted totransfer of the document file from the company application server 1305Ato an authorized location. Even though the company application server1305A may provide resources for the trusted application 1105A, theadministrative policy may block any transfers of sensitive informationfrom leaving the embedded browser 410.

Referring to FIG. 13C, depicted is a process diagram for an environment1360 for controlling traffic from the embedded browser 410. Theenvironment 1360 may include the components of the system 1100 describedherein above. The environment 1360 may include the embedded browser 410administered by a security operator 1310, a company application server1350A, and a rogue application server 1305B. The embedded browser 410may access a trusted application 1105A. The servers 1305A and 1305B maybe set as trusted or untrusted under an administrated policy set (e.g.,whitelist or blacklist) by the security operator 1310. In operation (1),the embedded browser 410 may access the company application 1305A viathe trusted application 1105A to retrieve a document file. Theadministrative policy may permit the trusted application 1105A to read,copy, and edit the document file, but may not allow movement of thedocument file to the rogue application 1305B (e.g., using a blacklist).In operation (2), a user of the embedded browser 410 may attempt to sendthe document file to the rogue application server 1305B. When the userattempts to send the document file to a personal application server1305B, the transfer of the document file may be blocked in accordancewith the administrative policy. In operation (3), the security operator1310 may be alerted as to the attempted to transfer of the document filefrom the company application server 1305A to the rogue applicationserver 1305B.

Referring to FIG. 14, depicted is a flow diagram of a method 1400 ofinspecting traffic exchanged with a network application accessed via aclient application. The functionalities of the method 1400 may beimplemented using, or performed by, the components detailed herein inconnection with FIGS. 1-13C. In brief overview, an application inspectormay monitor or intercept traffic routed via an embedded browserproviding access to an application hosted on a server (1405). Theapplication inspector may generate analytics data (1410). Theapplication inspector may update a user behavior model (1415). Theapplication inspector may determine whether to restrict data (1420).

In further detail, the application inspector may monitor or intercepttraffic routed via an embedded browser providing access to anapplication hosted on a server (1405). Network traffic may flow in theform of packets between the client running the embedded browser and oneor more servers hosting resources for the application. The packets maybe exchanged via a secure communications channel established between theclient and the one or more servers. Prior to the encryption and/ortransmission of packets from the embedded browser to the server, theapplication inspector may intercept the packets for analysis.

The application inspector may generate analytics data (1410). Theanalytics data may include computing resource performance metrics,network traffic performance metrics, and metadata in connection with theuse or operation of the application. In generating the analytics data,the application inspector may monitor computing resources on the clientrunning the embedded browser to determine the computing resourcesperformance metrics. The application inspector may also monitor thenetwork traffic to determine the network traffic performance metrics.Furthermore, the application inspector may identify metadata from thepackets exchanged between the client and the server as well as theembedded browser.

The application inspector may update a user behavior model (1415). Theuser behavior model may have a set of inputs, a set of weights, and aset of outputs to characterize or predict the user behavior with respectto the application. The application inspector may train the userbehavior model using the training data. The training data may includeanalytics data aggregated from multiple clients. With the accumulationof more analytics data, the application inspector may change or adjustthe set of weights in the user behavior model.

The application inspector may determine whether to restrict data (1420).The restriction of data by the embedded browser may be in accordancewith an administrative policy. The administrative policy may specifypackets containing potentially sensitive data are not to leave theclient device via the embedded browser. The potentially sensitive datamay be defined using regular expressions or formats. The administrativepolicy may also specify a black list of destination addresses to whichthe sensitive data is not to be transmitted. By applying theadministrative policy to the network traffic from the embedded browser,the application inspector may restrict or permit transmission of thepackets.

Referring now to FIG. 15, depicted is a flow diagram of a method 1500 ofmonitoring network applications. The functionalities of the method 1500may be implemented using, or performed by, the components detailedherein in connection with FIGS. 1-14. In brief overview, an analyticstracking engine of a client application may monitor traffic andresources (1505). The analytics tracking engine may generate analyticsdata (1510). A behavior modeler engine of the client application maytrain a user behavior model (1515). The behavior modeler engine mayprovide the user behavior model (1520). A data controller engine of theclient application may determine whether to restrict data (1525). If thedetermination is to restrict the data, the data controller engine mayrestrict the data (1530). Otherwise, if the determination is to notrestrict the data, the data controller engine may permit the data(1535).

In further detail, an analytics tracking engine (e.g., the analyticstracking engine 1135) of a client application (e.g., the clientapplication 404) may monitor traffic and resources (1505). The trafficmay include data (e.g., in the form packets) exchanged with a networkapplication (e.g., the application 1100) hosted on one or more servers(e.g., the server 430). The resources may include computing processingresources (e.g., response time, processor usage, processing time, memoryconsumption, hard disk consumption) of an a client (e.g., the client402) in accessing the network application. Through an embedded browser(e.g., the embedded browser 410), the client application may provideaccess to a set of network applications including the monitored networkapplication. The analytics tracking engine may perform telemetricmeasurements to monitor or track the traffic and resources.

To monitor the traffic, the analytics tracking engine may decrypt,decode and/or inspect the data exchanged via a secure communicationchannel between the client and the server. The secure communicationchannel may be established for exchanging data between the embeddedbrowser and the network application, In some embodiments, the analyticstracking engine may have visibility to the traffic originating from theclient running the embedded browser. With this visibility, the analyticstracking engine may monitor the traffic originating from the client,including from the client application and the embedded browser of theclient application. For example, the analytics tracking engine mayinspect each packet originating from the embedded browser of the clientapplication destined for the network application. From the inspection,the analytics tracking engine may determine a size, a number, andfrequency of packets, among other measures related to the traffic.

To monitor the resources, the analytics tracking engine may measure theresponse time, processor usage, processing time, memory consumption,and/or hard disk consumption, among others, on the client. The resourcesmay be related to the client accessing the network application. In someembodiments, the analytics tracking engine may monitor one or moreoperations performed in the embedded browser in accessing the networkapplication. The operations may include user interaction events,processes, and routines, among others, of the embedded browser accessingthe network application. For example, the analytics tracking engine mayaccess computing resources of the client to measure a subset of theresources consumed by the embedded browser in accessing the networkapplication. In some embodiments, the analytics tracking engine maymonitor for user interactions with the embedded browser (e.g., a userinterface of the embedded browser and/or a user interface of the networkapplication) in accessing the network application. In some embodiments,the analytics tracking engine may access a log of user interactionevents from the client for the embedded browser.

The analytics tracking engine may generate analytics data (1510). Inaccordance with the monitoring of the network application and theresources of the client, the analytics tracking engine may generate theanalytics data. The analytics data may include one or more computingresource performance metrics, one or more network traffic performancemetrics, and/or metadata. The computing resource performance metrics mayinclude a processor usage (sometimes referred to as CPU usage), aresponse time, a processing time (sometimes referred to as CPU time),memory consumption, and/or hard disk consumption, among others. Based onthe monitoring of the resources, the analytics tracking engine maygenerate the computing resource metrics of the analytics data. Thenetwork performance metrics may include network bandwidth consumption,network latency, a network throughput, session duration, an engagementtime, an interaction rate, and/or a packet exchange rate, among others.Based on the monitoring of the network application, the analyticstracking engine may generate the network traffic performance metrics ofthe analytics data. The metadata may include a location of the client,an account identifier of a user operating the embedded browser, aversion number of the client application, a version number of theembedded browser, and a network type of the secure communicationchannel, among others. From the monitoring of the network applicationand resources, the analytics tracking engine may gather and generate themetadata of the analytics data.

In some embodiments, the analytics tracking engine may acquireadditional analytics data form a telemetry tracking engine (e.g., thetelemetry tracking engine 1120). The telemetry tracking engine may havevisibility to the traffic originating from the network application, byhaving the client application and/or embedded browser terminate one endof the secure connection/session of the traffic. With this visibility,the telemetry tracking engine may monitor the traffic originating fromthe network application destined for the embedded browser of the clientapplication. The telemetry tracking engine may also generate theanalytics data related to the network performance metrics of the networkapplication accessed by the embedded browser of the client application.The analytics tracking engine may acquire the analytics data generatedby the telemetry tracking engine by requesting the telemetry trackingengine to provide the analytics data. Upon receipt, the analyticstracking engine may combine the analytics data generated by thetelemetry tracking engine with the analytics data generated by theanalytics tracking engine. In addition, the analytics tracking enginemay use the analytics data received from the telemetry tracking engineto generate the network traffic performance metrics.

A behavior modeler engine (e.g., the behavior modeler engine 1140) ofthe client application may train a user behavior model (1515). The userbehavior model may be a machine learning model (e.g., artificial neuralnetwork (ANN), support vector machine (SVM), Bayesian model, orregression model) to characterize and predict user interactions with thenetwork application. The user behavior model may include a set ofinputs, a set of outputs, and a set of weights to relate the inputs tothe outputs. The inputs may include information from monitoring thenetwork application or resources of the client in accessing the networkapplication, such as user interactions with the embedded browser. Theoutputs may include a predicted behavior of the user (e.g., userinteractions with the embedded browser in accessing the networkapplication). The outputs may also include a deviation measure betweenexpected user behavior and measured user behavior. In some embodiments,the outputs may include expected analytics data, including expectedcomputing resource metrics and expected network traffic metrics, amongothers.

Using the monitoring and the generated analytics data, the behaviormodeler engine may train the user behavior model. In some embodiments,the behavior modeler engine may aggregate the analytics data frommultiple embedded browsers running across different client applicationson various clients. The behavior modeler engine may use the informationfrom monitoring and the analytics data as a training dataset to modifyor adjust the weights of the user behavior model. In training the userbehavior model, the behavior modeler engine may feed the monitoredinformation as the inputs of the user behavior model. The monitoredinformation may include the measured user interactions of the embeddedbrowser in accessing the network application, such as user interactions.The user behavior model may generate a set of outputs from the inputusing the initial set of weights (e.g., set to random). The set ofoutputs may include expected user behavior from the inputs based on theset of weights of the user behavior model. The behavior modeler enginemay compare the expected user behavior outputted by the user behaviormodel and the measured user behavior. In some embodiments, the behaviormodeler engine may compare the expected measurements with the actualmeasurements (e.g., monitoring of the network application and theresources). From the comparison, the behavior modeler engine maycalculate or determine an error (e.g., mean square error (MSE) orroot-mean-square error (RMSE)) between the expected user behavior andthe monitored user behavior. The behavior modeler engine may set,modify, or adjust the set of weights based on the calculate error. Thebehavior modeler engine may continue to train the user behavior modeluntil convergence (e.g., when adjustment of weights is below a certainthreshold).

The behavior modeler engine may provide the user behavior model (1520).With the training of the user behavior model, the behavior modelerengine may use or provide the user behavior model to identify anomalousactivity associated with the network application accessed via theembedded browser. The anomalous activity may be indicative of suspiciousor abnormal user behavior with the embedded browser in accessing thenetwork application. Upon completion of the training, the behaviormodeler model may set the user behavior model to run-time mode toidentify the anomalous activity.

A data controller engine (e.g., the data controller engine 1145) of theclient application may determine whether to restrict data (1525). Thedata may include one or more packets exchanged between the embeddedbrowser of the client device and the network application via the securecommunication channel. In some embodiments, the packets in the data mayindicate operations (e.g., user interactions) on the embedded browser inaccessing the network application. At least one packet in the data maybe generated and sent by the embedded browser in response to anoperation on the embedded browser. In addition, at least one otherpacket in the data may be generated and sent by the network applicationin response to the packet associated with the operation. In someembodiments, the data controller engine may identify the operation onthe embedded browser from each packet. In some embodiments, the datacontroller engine may identify the data from the monitored trafficbetween the embedded browser and the server hosting the networkapplication. The data may include or may correspond to one or moreoperations, such as user interactions or processes of the embeddedbrowser in accessing the network application. In some embodiments, thedata controller engine may invoke the analytics tracking engine toretrieve analytics data. The retrieved analytics data may include thecomputing resource performance metrics, the network traffic performancemetrics, and the metadata, among others. The retrieved analytics datamay be generated using monitoring subsequent to the monitoring used totrain the user behavior model.

By applying the user behavior model, the data controller engine maycalculate, determine, or generate a deviation measure between theexpected user behavior and the measured user behavior. The userbehaviors may include the interaction events on the embedded browser inaccessing the network application. The deviation measure may indicate adegree of anomalousness between the expected user behavior and themeasured user behavior. The data controller may feed the retrievedanalytics data as the inputs of the user behavior model. The userbehavior model in turn may generate the expected user behavior from theinput based on the set of weights. The behavior modeler engine maycompare the expected user behavior outputted by the user behavior modeland the user behavior identified from the data exchanged between theembedded browser and the network application. From the comparison, thedata controller engine may calculate or determine the deviation measure(e.g., mean square error (MSE) or root-mean-square error (RMSE)) betweenthe expected user behavior and the monitored user behavior. With thecalculation, the data controller engine may compare the deviationmeasure to a threshold measure. The threshold measure may correspond toa deviation measure at which the corresponding data is to be restrictedor permitted. When the deviation measure is determined to be greaterthan the threshold measure, the data controller engine may determine torestrict the data corresponding to the measured user behavior.Conversely, when the deviation measure is determined to be less than orequal to the threshold measure, the data controller engine may determineto permit the data corresponding to the measured user behavior.

In some embodiments, the data controller engine may also determinewhether to restrict the data by applying a policy to the data. Thepolicy may specify a set of data types labeled that are to berestricted. For example, the policy may indicate that potentiallysensitive information (e.g., personally identifiable information (PII),health records, and financial records) are to be restricted. The policymay also specify a blacklist of domains that are to be restricted. Insome embodiments, the data controller engine may parse the data (e.g.,the packet) to identify the contents of the data. The data controllermay compare the contents to the information to the specifications of thepolicy. The contents may include information from the body or the headerof the packet (e.g., a source address). If the contents are determinedto match, the data controller may determine to restrict the data.Conversely, if the contents are determined to not match, the datacontroller may determine to permit the data.

If the determination is to restrict the data, the data controller enginemay restrict the data (1530). The determination may be based on the userbehavior model or the policy, or a combination of both, among others.The data controller may restrict, block, or prevent the transmission ofthe data from the embedded browser to the network application.Conversely, the data controller may restrict, block, or prevent theembedded browser from receiving or otherwise processing the data fromthe network application. Otherwise, if the determination is to notrestrict the data, the data controller engine may permit the data(1535). The data controller may allow the transmission of the data fromthe embedded browser to the network application. Conversely, the datacontroller may allow the embedded browser from receiving or otherwiseprocessing the data from the network application.

Various elements, which are described herein in the context of one ormore embodiments, may be provided separately or in any suitablesubcombination. For example, the processes described herein may beimplemented in hardware, software, or a combination thereof. Further,the processes described herein are not limited to the specificembodiments described. For example, the processes described herein arenot limited to the specific processing order described herein and,rather, process blocks may be re-ordered, combined, removed, orperformed in parallel or in serial, as necessary, to achieve the resultsset forth herein.

It should be understood that the systems described above may providemultiple ones of any or each of those components and these componentsmay be provided on either a standalone machine or, in some embodiments,on multiple machines in a distributed system. The systems and methodsdescribed above may be implemented as a method, apparatus or article ofmanufacture using programming and/or engineering techniques to producesoftware, firmware, hardware, or any combination thereof. In addition,the systems and methods described above may be provided as one or morecomputer-readable programs embodied on or in one or more articles ofmanufacture. The term “article of manufacture” as used herein isintended to encompass code or logic accessible from and embedded in oneor more computer-readable devices, firmware, programmable logic, memorydevices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g.,integrated circuit chip, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), etc.), electronicdevices, a computer readable non-volatile storage unit (e.g., CD-ROM,USB Flash memory, hard disk drive, etc.). The article of manufacture maybe accessible from a file server providing access to thecomputer-readable programs via a network transmission line, wirelesstransmission media, signals propagating through space, radio waves,infrared signals, etc. The article of manufacture may be a flash memorycard or a magnetic tape. The article of manufacture includes hardwarelogic as well as software or programmable code embedded in a computerreadable medium that is executed by a processor. In general, thecomputer-readable programs may be implemented in any programminglanguage, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte codelanguage such as JAVA. The software programs may be stored on or in oneor more articles of manufacture as object code.

While various embodiments of the methods and systems have beendescribed, these embodiments are illustrative and in no way limit thescope of the described methods or systems. Those having skill in therelevant art can effect changes to form and details of the describedmethods and systems without departing from the broadest scope of thedescribed methods and systems. Thus, the scope of the methods andsystems described herein should not be limited by any of theillustrative embodiments and should be defined in accordance with theaccompanying claims and their equivalents.

It will be further understood that various changes in the details,materials, and arrangements of the parts that have been described andillustrated herein may be made by those skilled in the art withoutdeparting from the scope of the following claims.

We claim:
 1. A method comprising: monitoring, by a client device, traffic of an application hosted on one or more remote computing devices and accessed via the client device; providing, by the client device responsive to monitoring, data associated with traffic of the application as input to a model, the model configured to output identification of a predicted behavior of a user responsive to the input; and causing, by the device, access to the application by the user to be restricted responsive to the identification of the predicted behavior of the user from using the model.
 2. The method of claim 1, further comprising accessing, by the client device, the application via browser within a client application of the client device.
 3. The method of claim 1, further comprising generating, by the client device from monitoring, the data identifying one or more interactions of the user with the application.
 4. The method of claim 1, further comprising determining, by the client device, a deviation from the predicted behavior and a behavior of the user measured from monitoring.
 5. The method of claim 1, further comprising determining, by the client device, to restrict access to the application responsive to the deviation being greater than a threshold.
 6. The method of claim 1, further comprising using, by the client device, one or more weights with the model, the one or more weights determined based at least on the data.
 7. The method of claim 1, wherein the data comprises one or more of a metric of a computing resource of the client device or a metric of the traffic.
 8. A client device comprising: one or more processors, coupled to memory and configured to: monitor traffic of an application hosted on one or more remote computing devices and accessed via the client device; provide, responsive to monitoring, data associated with traffic of the application as input to a model, the model configured to output identification of a predicted behavior of a user responsive to the input; and cause access to the application by the user to be restricted responsive to the identification of the predicted behavior of the user from using the model.
 9. The client device of claim 8, wherein the one or more processors are further configured to access the application via browser within a client application of the client device.
 10. The client device of claim 8, wherein the one or more processors are further configured to generate, from monitoring, the data identifying one or more interactions of the user with the application.
 11. The client device of claim 8, wherein the one or more processors are further configured to determine a deviation from the predicted behavior and a behavior of the user measured from monitoring.
 12. The client device of claim 11, wherein the one or more processors are further configured to determine to restrict access to the application responsive to the deviation being greater than a threshold.
 13. The client device of claim 8, wherein the one or more processors are further configured to use one or more weights with the model, the one or more weights determined based at least on the data.
 14. The client device of claim 8, wherein the data comprises one or more of a metric of a computing resource of the client device or a metric of the traffic.
 15. A non-transitory computer readable medium storing program instructions for causing one or more processors of a client device to: monitor traffic of an application hosted on one or more remote computing devices and accessed via the client device; provide, responsive to monitoring, data associated with traffic of the application as input to a model, the model configured to output identification of a predicted behavior of a user responsive to the input; and cause access to the application by the user to be restricted responsive to the identification of the predicted behavior of the user from using the model.
 16. The non-transitory computer readable medium of claim 17, wherein the program instructions further cause the one or more processors to generate, from monitoring, the data identifying one or more interactions of the user with the application.
 17. The non-transitory computer readable medium of claim 17, wherein the program instructions further cause the one or more processors to determine a deviation from the predicted behavior and a behavior of the user measured from monitoring.
 18. The non-transitory computer readable medium of claim 17, wherein the program instructions further cause the one or more processors to determine to restrict access to the application responsive to the deviation being greater than a threshold.
 19. The non-transitory computer readable medium of claim 17, wherein the program instructions further cause the one or more processors to use one or more weights with the model, the one or more weights determined based at least on the data.
 20. The non-transitory computer readable medium of claim 17, wherein the data comprises one or more of a metric of a computing resource of the client device or a metric of the traffic. 